------- Comment #46 from howarth at nitro dot med dot uc dot edu 2010-08-11 13:14 ------- (In reply to comment #44) > I do not think the current solution is complete/correct.
Don't confuse the darwin9 and darwin10 unwinder issues. They are different incompatiibilities with the darwin unwinder. Also keep in mind that darwin9 uses an unwinder derived from libgcc whereas darwin10 uses a compatibility unwinder from libSystem. > Taking the case of Darwin9/OSX 10.5: > > (a) the code for _Unwind_FindEnclosingFunction &c. as posted on > http://www.opensource.apple.com/release/mac-os-x-1058/ is the same as fsf-gcc > (AFAICT from browsing it online) -- so I'm not sure why we added in the > darwin10_Unwind_FindEnclosingFunction (it's the same code as already present > in > the system lib). [having said that, even if the system code _is_ broken and > unusable, (b) applies. and one needs to work around the breakage without > bypassing said system code] > Read http://gcc.gnu.org/ml/gcc-patches/2009-12/msg00998.html which explains the logic of re-exporting _Unwind_FindEnclosingFunction() under a different name for darwin10. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41991
