Dear colleagues,
Unfortunately I was too fast to get 680M - there is currently no
debuggable developer driver for it, probably untill September. But I
need to get our dynamic code loader (joint work with Yunqing) running
on Kepler. At first, kernel successfully loads and runs, but when I'm
trying to run it again with some instruction modified, it throws error
700. This error status may mean a wide range of issues, and it's hard
to guess what the problem is. Debugger would help, but until September
my 680M is useless for that.
Is it correct that normal 680 is currently already debuggable? If yes,
and you have one on short hand, I'd kindly ask to make the following
test and dump the results here:
$ svn co
http://asfermi.googlecode.com/svn/branches/libasfermi libasfermi
$ cd libasfermi/tests/dyloader/
$ make test1
$ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:.:../.. ./test1 100
Test should fail. Please relaunch it under cuda-gdb (only works with
developer driver):
$ LD_LIBRARY_PATH=$LD_LIBRARY_PATH:.:../.. cuda-gdb ./test1
$ cuda set break_on_launch application
$ r 100
$ c
$ disass
So, break on every user kernel launch, run, continue after first break
and disass the point of the crash. It would be important to know:
1) How the top part of kernel looks like
2) At what address program crashed
Thanks,
- Dima.