Re: [Pyobjc-dev] Objects/stringobject.c:110: failed assertion `str != NULL'; might involve PyObjc

[Ronald O. <ron...@ma...>]

On 8-feb-2006, at 21:11, Bob Ippolito wrote:

>
> On Feb 8, 2006, at 11:46 AM, Phil Frost wrote:
>
>> I've been getting an intermittent sigabrt in my program. I am using
>> PyObjc version 1.3.7. I haven't yet been able to determine the cause,
>> but I noticed PyObjCClass_New isn't too far down in the backtrace. I
>> don't know if pyobjc is doing something bad, or if I'm giving it some
>> bad input, but here's the backtrace; maybe it's more helpful for  
>> someone
>> else:
>
> Try it with Python 2.4.  Could be a bug in Python 2.3.

Testing with PyObjC HEAD would be more interesting.

The stack trace indicates that the __getattribute__ method for objc  
objects
is called for a class that doesn't have a name?!? That shouldn't  
happen. This
might mean you have bad memory managment elsewhere in the program  
(that is,
a method is called on the Python proxy for an objc object that was  
already
garbage collected by ObjC).

If you catch the signal in gdb you could find the name of the method  
in the
call to method_stub, the name is in args[1] (or rather in *(char**) 
(args[1])),
this might give you an indication on what object is causing problems.

As always I'm interested in a simple program that demonstrates the  
problem,
but that might be a problem in this case :-)

Ronald

>
> -bob
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through  
> log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD  
> SPLUNK!
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev