Re: C++ exceptions with OpenBSD 3.6 on amd64

2005-10-21 Thread Daniel Ouellet
Chad M Stewart wrote: And if you'd pre-ordered 3.8 then you might have gotten an email like I did today. :-) Now I just need enough revenue from my new company so I can replace all of my "servers" with real boxes like V20z and X4100. Funny now that I'm now longer an employee of Sun I'll p

Re: C++ exceptions with OpenBSD 3.6 on amd64

2005-10-21 Thread Chad M Stewart
On Oct 21, 2005, at 2:16 PM, Sebastian Cufre wrote: Well, the problem is that with OpenBSD 3.7 other thing doesn't work (php4-xslt makes apache crash when used), and OpenBSD 3.8 is no yet released officially. And if you'd pre-ordered 3.8 then you might have gotten an email like I did tod

Re: C++ exceptions with OpenBSD 3.6 on amd64

2005-10-21 Thread Marc Espie
On Fri, Oct 21, 2005 at 03:16:13PM -0300, Sebastian Cufre wrote: > Well, the problem is that with OpenBSD 3.7 other thing doesn't work > (php4-xslt makes apache crash when used), and OpenBSD 3.8 is no yet released > officially. > > On 10/21/05, Peter Valchev <[EMAIL PROTECTED]> wrote: > > > > > I

Re: C++ exceptions with OpenBSD 3.6 on amd64

2005-10-21 Thread Sebastian Cufre
Well, the problem is that with OpenBSD 3.7 other thing doesn't work (php4-xslt makes apache crash when used), and OpenBSD 3.8 is no yet released officially. On 10/21/05, Peter Valchev <[EMAIL PROTECTED]> wrote: > > > I have a simple c++ program that throws an exception and tries to catch > it. > >

Re: C++ exceptions with OpenBSD 3.6 on amd64

2005-10-21 Thread Peter Valchev
> I have a simple c++ program that throws an exception and tries to catch it. > But when I run it, it crashes with segmentation faul. Looking and the stack > trace, looks like the exception is thrown but no one catches it. Is this a > bug? There's a workaround? Not sure when, but this has been fix

C++ exceptions with OpenBSD 3.6 on amd64

2005-10-21 Thread Sebastian Cufre
I have a simple c++ program that throws an exception and tries to catch it. But when I run it, it crashes with segmentation faul. Looking and the stack trace, looks like the exception is thrown but no one catches it. Is this a bug? There's a workaround? The c++ file is: --- include int main(void