-
|
Most of the rust compatible variables could reveal their values during debugging. However arrayfire array will only show something like I have tried the cpu backend. The situation is the same. I wonder whether there is any mean to show the value of arrayfire array during code debugging? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
You should be able to view debugging information using Also, please do note that, even with gdb you still won't be able to view array contents itself directly in a debugger since gdb/lldb or any debugger for that matter cannot provide you a view of the GPU memory. You can use the list of functions for viewing the array contents. Metadata, such as dimensions, type of data etc., of any given error would be visible in debugger though. |
Beta Was this translation helpful? Give feedback.
You should be able to view debugging information using
gdb, orlldbI think (I haven't tried lldb myself, but should work). Which tool are you using ?Also, please do note that, even with gdb you still won't be able to view array contents itself directly in a debugger since gdb/lldb or any debugger for that matter cannot provide you a view of the GPU memory. You can use the list of functions for viewing the array contents. Metadata, such as dimensions, type of data etc., of any given error would be visible in debugger though.