I was unable to solve the launch timeouts by removing elements of the kernel code.
This seemed to me to point to a problem with CUDA, after reinstalling Windows (XP Pro SP3), CUDA, etc., the program executes correctly when packaged. I am now unable to reproduce the error. As such it would seem that when Windows/CUDA is playing ball py2exe seems able to handle pycuda 'out of the box'. The distutils script must explicitly include the pyCuda header files, and exclude nvcudal.dll. Many thanks for your time. Regards, Sam. -----Original Message----- From: Andreas Kloeckner [mailto:li...@informa.tiker.net] Sent: 21 May 2010 13:56 To: Samuel Powell; pycuda@tiker.net Subject: RE: [PyCUDA] PyCuda Launch Timeout under Py2Exe On Fri, 21 May 2010 13:24:51 +0100, "Samuel Powell" <spow...@medphys.ucl.ac.uk> wrote: > Hi Andreas, > > You are correct in your assertion. > > I followed your advice by packaging some of the pyCuda example scripts > using py2exe before executing them. In the majority of cases, I found > no problem executing the packaged code. > > If, as you suggest, the launch failure is likely caused by a segfault > on the device, I think the best course of action is for me to dissect > the CUDA kernel until it runs correctly, thus identifying where the > bad addressing comes into play. > > Would you agree with this analysis? That sounds plausible. Good luck with your bug hunting, Andreas PS: Please keep the list cc'd when replying. Thx! _______________________________________________ PyCUDA mailing list PyCUDA@tiker.net http://lists.tiker.net/listinfo/pycuda
