P.S. Please can you check that -fexceptions is being passed to clang. -fobjc-exceptions doesn't seem to do anything in 3.0 (I thought it implied -fexceptions in 2.9, but I could be wrong). If this is the problem, then it's an easy fix.
David On 27 Oct 2011, at 12:33, David Chisnall wrote: > On 27 Oct 2011, at 09:14, Richard Frith-Macdonald wrote: > >> Is this the compiler passing the wrong value, or possibly something wrong in >> the objc library? > > Neither - this is the correct behaviour. That method doesn't exist, and > trying to call it is supposed to throw an exception. The problem is not that > the exception is thrown, it is that it is not caught. > > This means that either: > > - There is a bug in libobjc2's exception handling, or > - One of your stack frames does not have unwind information. > > One of the bug changes that LLVM 3.0 made over 2.9 was to emit .cfi* > directives in the assembler, instead of emitting the unwind tables directly. > Do you get any warnings from the assembler about unknown directives when you > compile? Do simple @throw / @catch tests pass for you? What about C++ > exceptions (Sebastian - did you check that on OpenBSD?) > > David > > -- > This email complies with ISO 3103 > > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/discuss-gnustep -- Sent from my brain _______________________________________________ Discuss-gnustep mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnustep
