Re: [Pyobjc-dev] Crashes in PyObjCInitNULL
Brought to you by:
ronaldoussoren
From: Ronald O. <ron...@ma...> - 2006-12-30 09:01:42
|
On 29 Dec, 2006, at 20:10, Michael Tsai wrote: > On Dec 29, 2006, at 1:15 PM, Ronald Oussoren wrote: > >> Sounds like a reference count problem "somewhere". InitNULL should >> be called only one time and creates a singleton object (objc.NULL) >> which most people probably will never use. > > Is it expected that PyObjCInitNULL would be called from > _PyType_Lookup? From the source, it looks to me like it's only called > from init_objc (and isn't registered in any tables). It should indeed only be called from init_objc. Odd stacktraces like this are often a sign of memory managment problems. Is you're program a python program or are you embedding Python/PyObjC in another program? Ronald > > --Michael > > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Pyobjc-dev mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyobjc-dev |