Thanks Andreas for the advice, I tried to import pycuda.driver like you said and there was an error message that popped up, I searched this message on google and found someone else had the same problem ( http://www.nabble.com/Incorrect-libjpeg.dylib-after-installing-ImageMagick-td22625866.html). The issue went back to my .bash_profile and the fact that I had defined a DYLD_LIBRARY_PATH that didn't belong. I deleted the line and restarted my terminal to find that most things are working now. Nothing hangs and several of the test and example programs run just fine.
Thanks for all of the help! Ashleigh On Thu, Jun 18, 2009 at 5:51 AM, Andreas Klöckner <[email protected]>wrote: > On Donnerstag 18 Juni 2009, ashleigh baumgardner wrote: > > Yes, it hung on test_driver.py and all of the others. I tried what you > > suggested, turning CUDA_TRACE to True and then recompiling, but sadly it > > has turned up nothing. The program still hangs and a control c does not > > make it exit. I'm stumped, does anyone have any other thoughts? Please? > > If Macs have strace, you can try that. (i.e. strace -o syscall.log python > test_driver.py) strace displays the system calls that a program is carrying > out. From that, it might be easier to determine the culprit. > > It's also strange that you don't get *anything* from the API trace. That > makes > it likely that CUDA is not at fault. Can you try starting Python and then > manually import pycuda.driver? Does it hang? If so, at what stage? Try the > same with "python -v". > > Andreas > > _______________________________________________ > PyCUDA mailing list > [email protected] > http://tiker.net/mailman/listinfo/pycuda_tiker.net > >
_______________________________________________ PyCUDA mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
