Hi-
I’m using gdb, and it seems to get the line numbers in files all screwed up as soon as it hits a kernel call, i.e…
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0x01733000
[Switching to process 37363 thread 0x1f603]
0x00004d7d in __globfunc__Z18multiply_AB_kernelPfS_S_iii () at main.cpp:532
main.cpp:532 is right at the end of my main.cpp file, so the debugger is seeing the kernel code as if it is appended to “main.cpp” instead of being aware of the “kernels.cu” file were the kernel actually sits.
I’m looking forward to a cuda aware gdb version on os x, if one is in the works! There is a linux port, so here’s hoping a mac port isn’t too far away!
Cheers,
Drew