On Tue, Mar 17, 2009 at 21:35, Andreas Klöckner <[email protected]>wrote:
> On Mittwoch 18 März 2009, Nicholas Tung wrote: > > Did you get the messages below? Not much reply necessary, but that > > [1-line] bug should be fixed. > > Yes, I had gotten them. And then I also managed to forget about them. > Sorry > about that. No worries, thanks! > > >> Also, do you typically build using python setup.py build? > > Yes. > > > >> It doesn't > > >> seem to detect c++ file changes for me... > > Distutils kinda sucks. It does detect changes in the .cpp files, but not in > any included headers. rm -Rf build, python setup.py install. Ick. :) Haha, okay, that's what I had been doing :). > > > By the way, I know this is probably my problem, but have you ever > > > encountered, "Fatal Python error: GC object already tracked" > > No, not that I recall. Sorry I forgot to update that, I actually encountered this bug doing multi-threaded PIL image loading alone, so it's probably not related (or Python multi-threading isn't as good as it could be...) > > > For some reason, my multithreaded code isn't printing stack traces > where > > > I'd like it to... any suggestions would be helpful (can pdb handle mt > > > code well?) > > I have nearly no experience with threaded Python code, and I'm not too keen > on > changing that. For good reason :) Thanks, Nicholas
_______________________________________________ PyCuda mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
