[Pyobjc-dev] Re: debugging pyobjc
Brought to you by:
ronaldoussoren
From: Michael H. <mw...@py...> - 2004-01-23 10:24:53
|
Ronald Oussoren <ous...@ci...> writes: > On 22 jan 2004, at 17:21, Michael Hudson wrote: > >> Michael Hudson <mw...@py...> writes: >> >>> I'm vaguely trying to track down a bug in recent versions of pygame on >>> MacOS X, which now uses PyObjC. So, after much wailing and gnashing >>> of teeth (see pythonmac-sig) I have a debugging framework install of >>> Python, and seem to have built pyobjc against it. >>> >>> 1) PyObjC's setup.py seems to unconditionally pass -O3 to the >>> compiler. This is, um, contrary to the spirit of a debug build. >>> What's wrong with the value of CFLAGS you get by default (from >>> $(prefix)/lib/python$(VERSION)/config/Makefile)? > > I'll change those, the defaults should be good enough. Ta. >>> >>> 2) Stuff like this isn't encouraging: >>> [snippety] >>> >>> Am I in new territory here? >> >> Actually I'm seeing runPyObjCtests (or whatever that script's called) >> dump core when run against today's CVS built against a release Python. >> So I think there may be real problems here. > > Do you by any change have a machine without a G4 processor? Yes... > The setup.py also sets some flags for G4 specific compilation. Those > will also be removed. Thanks. I thought I'd hacked them out too, but maybe not. I did get some "Illegal Instruction" crashes as well, which was perhaps a clue... > I'm currently rebuilding PyObjC to check for problems. One thing you > might try is removing the existing PyObjC installation before > installing a new one (if you have one installed). In my quest (sp?) > for faster loading times I've moved some of the extensions. I think I may have made this mistake as well yesterday. Last night I built a fresh PyObjC and actually used it successfully, so the problems can't be that severe. I didn't dare run the tests, though :-) (I had a bad day wrt computers yesterday). Cheers, mwh -- 40. There are two ways to write error-free programs; only the third one works. -- Alan Perlis, http://www.cs.yale.edu/homes/perlis-alan/quotes.html |