Re: Universal binary crash on quit on 10.3.9
Re: Universal binary crash on quit on 10.3.9
- Subject: Re: Universal binary crash on quit on 10.3.9
- From: Jim Wintermyre <email@hidden>
- Date: Mon, 4 Dec 2006 19:53:49 -0800
Here's a blast from the (recent) past:
James W. Walker wrote:
On 2 Jun 2006 I wrote:
>My universal binary crashes on quit on 10.3.9. No problem on Tiger,
>either PowerPC or Intel.
>
>Exception: EXC_BAD_ACCESS (0x0001)
>Codes: KERN_INVALID_ADDRESS (0x0001) at 0x09e323bc
>
>Thread 0 Crashed:
>0 <<00000000>> 0x09e323bc 0 + 0x9e323bc
>1 com.frameforge3d.frameforge2 0x00003a18 our_atexit + 0x7c
>(crt.c:355)
>2 libSystem.B.dylib 0x9002ce58 exit + 0x58
>3 com.frameforge3d.frameforge2 0x000026e8 _start + 0x158 (crt.c:249)
>4 com.frameforge3d.frameforge2 0x0000258c start + 0x3c
>
>If I do it while remote debugging, the debugger highlights line 76
>of iostream,
>
>static ios_base::Init __ioinit;
>
>Anyone have a hint of what this means or where to look?
I have a little more information about this. If I disable a plug-in
bundle, the crash stops happening. When I built the plug-in with
CodeWarrior, I had to make its CALL_ON_UNLOAD function call a
Metrowerks runtime library function, __destroy_global_chain(), to get
things cleaned up properly. Is there any analogous function for
Xcode?
Has anyone else seen anything like this? James, did you ever get
this figured out? I'm seeing a similar problem over here. In my
case, these are VST and AudioUnit plugins, which link to a framework
which is also ours. The crash only happens in 10.3.9, and happens
when the plugin host app quits, if it has instantiated one of our
plugins. It seems to have to do with static variable cleanup. It
doesn't happen in *all* plugin host apps, but in the ones where it
does crash, it always crashes in this same place. I do use Mach-O
init/term functions via __attribute__((constructor)) and
((destructor)) - though if I remove at least the term functions it
doesn't seem to matter. I the CodeWarrior CFM case, I was using CFM
init/term functions, with the init function calling __initialize() in
MSL DropinRuntime.Lib, and the term function calling __terminate().
I never found equivalent Mach-O/XCode functions, and they didn't
appear to be necessary, well at least until now.
Another data point is that if I build the same plugin in CodeWarrior,
it works fine. In that case I'm linking against the Mach-O version
of MSL, so this would seem to point to some weirdness with libs XCode
is linking to on 10.3.9.
Any ideas?
Thanks,
Jim
_______________________________________________
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