20 Jun
2014
20 Jun
'14
2:31 p.m.
Hi All,
I just installed PyCuda and got it working on my Windows 8.1 laptop. I'm
able to run the examples in VS 2010. My question concerns the 'preferred'
development environment for PyCuda: While it runs on Windows, I'm not able to
debug any kernel code using VS (Nvidia's Nsight) like I can using C/C++. I've
seen a bunch of threads concerning 'cuda-gdb' which leads me to believe folks
are using the command line on Linux to run PyCuda. Is this the 'preferred'
environment to run/debug PyCuda? Is there a way to debug the kernels in
PyCuda in Windows with/without VS Nsight or are we forced to use a command
line interface for debugging purposes?
Thanks,
Daniel
20 Jun
20 Jun
7:26 p.m.
Hi Daniel,
Daniel <daniel.pagan(a)andphysicsforall.com> writes:
I just installed PyCuda and got it working on my
Windows 8.1 laptop. I'm
able to run the examples in VS 2010. My question concerns the 'preferred'
development environment for PyCuda: While it runs on Windows, I'm not able to
debug any kernel code using VS (Nvidia's Nsight) like I can using C/C++. I've
seen a bunch of threads concerning 'cuda-gdb' which leads me to believe folks
are using the command line on Linux to run PyCuda. Is this the 'preferred'
environment to run/debug PyCuda? Is there a way to debug the kernels in
PyCuda in Windows with/without VS Nsight or are we forced to use a command
line interface for debugging purposes?
this question suggests a way to feed PyCUDA programs to Nvidia's GUI
tools (admittedly, in Linux):
https://stackoverflow.com/questions/13188049/how-to-profile-pycuda-code-wit…
Is there perhaps an equivalent Windows way to sell either the script or
the Python interpreter to VS as the 'executable' and to then debug that?
Is VS able/willing to debug executables it hasn't compiled itself?
(Sorry, as you can tell, I'm not much of a Windows guy... Hope this
helps at least a little.)
Andreas
23 Jun
23 Jun
4:01 p.m.
Andreas Kloeckner <lists@...> writes:
Is there perhaps an equivalent Windows way to sell either the script or
the Python interpreter to VS as the 'executable' and to then debug that?
Is VS able/willing to debug executables it hasn't compiled itself?
(Sorry, as you can tell, I'm not much of a Windows guy... Hope this
helps at least a little.)
Andreas
_______________________________________________
PyCUDA mailing list
PyCUDA <at> tiker.net
http://lists.tiker.net/listinfo/pycuda
Thanks for this, Andreas. I will try to profile some simple PyCuda code
with the VS profiler as in the above posts, then will experiment to see
how/if I can get the debugger to work. Hopefully I will have some results to
report.
What environment are you/other folks using? Are you just using command-line
editing in Linux; Are you using any IDE?
Thanks,
Daniel
29 Jun
29 Jun
7:28 p.m.
Daniel Pagan <daniel.pagan(a)andphysicsforall.com> writes:
Thanks for this, Andreas. I will try to profile some
simple PyCuda code
with the VS profiler as in the above posts, then will experiment to see
how/if I can get the debugger to work. Hopefully I will have some results to
report.
What environment are you/other folks using? Are you just using command-line
editing in Linux; Are you using any IDE?
I'm a command line guy, FWIW. I wrote pudb [1] in part because I found
existing IDE and debugging tools heavyweight and overly mouse-reliant.
Andreas
[1] https://pypi.python.org/pypi/pudb
2443
days inactive
2452
days old
3 comments
3 participants
participants (3)
-
Andreas Kloeckner -
Daniel -
Daniel Pagan