Cuda-gdb on Mavericks

Developer Tools CUDA Developer Tools CUDA-GDB
1

Does cuds-gdb work with Mac Desktop UI?

I have installed the newest cuda-mac-5.5.28_10.9_64 package.

When I try to test cuds-gdb bit reverse

(cuda-gdb) run
Starting program: /Users/baicai/Dropbox/GPU/CUDA/cuda_gdb test/bitreverse
warning: Could not open OSO archive file “/BinaryCache/Libsyscall/Libsyscall-2422.75.4~1/Symbols/BuiltProducts/libsystem_kernel.a”
warning: /private/var/tmp/Libsyscall/Libsyscall-2422.75.4~1/Libsyscall.build/Libsyscall_dynamic.build/Objects-normal/x86_64/_libc_funcptr.o': can't open to read symbols: No such file or directory. ... Breakpoint 1, main () at bitreverse.cu:23 23 unsigned int *d = NULL; int i; (cuda-gdb) continue Continuing. warning: /private/var/tmp/OSServices/OSServices-600.4~218/OSServices.build/OSServices.build/Objects-normal/x86_64/AppleIDAuthenticationClient.o’: can’t open to read symbols: No such file or directory.
…
warning: Could not open OSO archive file “/usr/local/UmbrellaPieces/Libraries/libSecurityCore.a”
[New Thread 0x1633 of process 499]
[Context Create of context 0x102802200 on Device 0]
A device about to be used for compute may already be in use for graphics.
This is an unsupported scenario. Further debugging might be unsafe. Aborting.
Disable the ‘cuda gpu_busy_check’ option to bypass the checking mechanism.

2

CUDA-GDB is supported on Mavericks.

Are those warning messages preventing you from debugging?
Are you using a beta version of Mavericks?

3

Thanks. These warnigns are fine, when I use console.

But when I debug in desktop, I got a message :

A device about to be used for compute may already be in use for graphics.
This is an unsupported scenario. Further debugging might be unsafe. Aborting.
Disable the ‘cuda gpu_busy_check’ option to bypass the checking mechanism.

Is there a way I can debug on desktop or use nsight?

I am using 13 rmbp 15 with intel and nvidia GPU.

Thanks.

4

Debugging with the window server running (desktop) on Mac is only supported when the device is not used for graphics. This is what they debugger ‘cuda gpu_busy_check’ verifies. You can override it at your own risks. If the device is used for display, hitting a breakpoint in your cuda application will freeze the display.

To help mitigate the problem, you can try to:

  • disable any form of hardware acceleration
  • do not use anything openGL and the like
  • disable Automatic Graphics Switching in the System Settings->Energy Saver tab.

Some more information can be found at http://docs.nvidia.com/cuda/cuda-gdb/index.html#single-gpu-debugging