Cuda-gdb can not see the hex of sass code

Developer Tools CUDA Developer Tools CUDA-GDB
1

Hi!
I am using cuda-gdb to debug some optimized code(without -G), in sass.
While i use : x/i $pc
I get
=> 0x7fffd5266280 <_Z5hellov+384>: CALL.ABS.NOINC 0x0
I want to check the actual hex of the sass code, like nvdisasm does. I use: x/10x $pc
I get all zeros
0x7fffd5266280 <_Z5hellov+384>: 0x00000000 0x00000000 0x00000000 0x00000000
0x7fffd5266290 <_Z5hellov+400>: 0x00000000 0x00000000 0x00000000 0x00000000
0x7fffd52662a0 <_Z5hellov+416>: 0x00000000 0x00000000

Is there a way to get the hex of running(dynamic) sass code, like nvdisasm do? nvdisasm only get the code before load into GPU DRAM.
Thanks a lot for the help!

2

Hi - thanks for reaching out!

CUDA-GDB makes use of cuobjdump in an indirect way when displaying disassembly. We do not capture the instruction byte code directly like what is done for other architectures inside gdb and thus have no way of displaying this information today. We will consider this feature request for inclusion in a future release.

Another feature you should be aware of is:

(cuda-gdb) set cuda disassemble_from device_memory

When set to device_memory, we will disassemble the actual instructions as they exist on the device, which may be different than what we obtain from the cubin that was originally loaded at kernel launch.

3

That helps a lot. Thanks for the help!