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.
> >> Also, I think you have a bug...
> >>
> >> ~device_allocation()
> >> {
> >> if (m_valid)
> >> free();
> >> }
> >>
> >> however,
> >> ~pooled_allocation()
> >> { free(); }
Well-spotted. Fixed in git.
> >> 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. :)
> > 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.
> > 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.
Andreas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ PyCuda mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
