PyObjC

On 29 Dec, 2006, at 18:36, Michael Tsai wrote:

> It hasn't happened on my Mac, so I couldn't look at it in the
> debugger, but I've received lots of crash reports from my customers
> (on both PowerPC- and Intel-based Macs) inside PyObjCInitNULL. Has
> anyone else seen this or know what the cause might be?

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.

Ronald

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).

--Michael

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
> Pyobjc-dev@...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

On Dec 30, 2006, at 4:01 AM, Ronald Oussoren wrote:

> 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?

It's a PyObjC app that includes a few Objective-C frameworks.

--Michael