Re: Building on 10.4, targeting 10.3.9+ unsuccessful
Re: Building on 10.4, targeting 10.3.9+ unsuccessful
- Subject: Re: Building on 10.4, targeting 10.3.9+ unsuccessful
- From: "Christopher Ashworth" <email@hidden>
- Date: Wed, 23 Nov 2005 17:58:48 -0500 (EST)
Despite Daniel's helpful clarification--(I had been misunderstanding how
to read a crash log; sorry 'bout that)--I am still very confused. Here's
why:
The particular line that is crashing my code is a simple [[MyClass alloc]
init] line. Commenting out or reorganzing the offending line invariably
leads to the same crash from some other attempt to alloc & init one of my
classes. The alloc & init methods of any of these classes are never
called, even though the classes apparently exist because I check for them
in the list of available classes. (I don't have the code in front of me
right now so I don't remember the particular C function that is used for
this...)
I copied my source to a 10.3.9 machine, installed a copy of XCode 1.0, and
compiled the code again. It runs without crashing on 10.3.9.
Another odd symptom: During startup I look for and load a set of plugins.
I use the isSubclassOfClass: during a series of validation checks to make
sure the bundle is a well-formed plugin. In the version of the program
compiled on 10.4.3 and run on 10.3.9, this method claims that none of my
plugins are a subclass of the parent which they are, in fact, a subclass
of. Checking the myClass->super_class field says the parent is the
expected one, but the isSubclassOfClass: method fails nonetheless. This
is really weird, and I am at a loss for why this could be happening.
This combination of wackiness is beyond my compiler/linker experience, and
I'm really stumped.
I hope I didn't miss another simple check that I should have done first
before posting to the list. If so I apologize in advance!
Regards,
Christopher
> The single most interesting thing you could do at this point is to
> break in your own code at [Workspace init]+80, and see what it's
> trying to do.
>
> When you've got your own code in the backtrace, you will solve your
> problem faster by looking at what it's doing before googling,
> tweaking settings, or posting to mailing lists.
>
> Daniel
>
> On Nov 21, 2005, at 10:56 PM, Christopher Ashworth wrote:
>
>> Thread 0 Crashed:
>> 0 libobjc.A.dylib 0x9086be80 _objc_trap + 0
>> 1 libobjc.A.dylib 0x9086be14 _objc_fatal + 0x48
>> 2 libobjc.A.dylib 0x908629c0 class_initialize + 0x120
>> 3 libobjc.A.dylib 0x90861524
>> _class_lookupMethodAndLoadCache + 0x84
>> 4 libobjc.A.dylib 0x90861298 objc_msgSend + 0xb8
>> 5 libobjc.A.dylib 0x908629e0 class_initialize + 0x140
>> 6 libobjc.A.dylib 0x90861524
>> _class_lookupMethodAndLoadCache + 0x84
>> 7 libobjc.A.dylib 0x90861298 objc_msgSend + 0xb8
>> 8 com.figure53.qlab 0x00007998 -[Workspace init] + 0x80
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden