On Fri, Jan 2, 2009 at 4:03 PM, Jonathan Schleifer
<js-openbsd-misc@webkeks.org> wrote:
quoted text
> Now if you compile it with egcc -fexceptions test.m -lobjc (you need
> GCC 4.x), it will just abort. It will do the same on any other OS if you
> don't specify -fexception or didn't catch the exception anywhere.
> However, it doesn't make any difference on OpenBSD whether you specify
> -fexceptions or not. Which is why I'm wondering: What's wrong here? Are
> we missing exception support in the OpenBSD libc? If so, wouldn't that
> give trouble with C++ as well? Or do I just need to specify some extra
> flags on OpenBSD?

Well, libc doesn't have any support for exceptions, but that's because
c doesn't have exceptions.  (not the problem).  It's possible that the
libstdc++ built with gcc 4 doesn't have exception support, or maybe
the objective c compiler doesn't, or it links with the wrong library,
or one of a million things that arent turned on because some esoteric
autoconf check failed.  Did you check if a c++ program exhibits the
same problem?