On Oct 18, 2011, at 4:58 AM, Iain Sandoe wrote: > The audit trail in the PR contains the detective work (mostly by Eric) that > concludes we have a long-standing bug in the Darwin x86-64 sigtramp unwind > data.
Yeah, well, it is a bug, if they ever fix it. If they burn it in and define it as correct, then, it is an unfortunatism. If they fix it, it should be software updated to older system and all tools fixed to use the new scheme. I suspect they'll never fix it. > This has been filed as radar #10302855, but we need a work-around until that > is resolved (possibly forever on older systems). > +#if defined (__x86_64__) If this is for a target machine compile, this is fine. Looking through the code, it seems like target machine code, though, I wasn't sure. If it is for host code, then this isn't cross compile safe. For host code DARWIN_X86 and TARGET_64BIT (from tm.h) both need to be true, for one to be compiling for a 64-bit x86 machine. I think this is fine for relevant release branches.
