C++ exceptions are broken in FreeBSD with gcc-compiled code?

I am unable to make a C++ program to catch an exception using the the system g++ compiler. > cat exc.C #include #include using namespace std; int main() { try { throw string("String"); } catch (string s) { cout << "Caught an exception \"" << s << "\"\n"; } } * Failed attempts with

Re: C++ exceptions are broken in FreeBSD with gcc-compiled code?

On Wed, Apr 09, 2008 at 09:39:09AM -0700, Yuri wrote: > I am unable to make a C++ program to catch an exception using the the > system g++ compiler. > > > cat exc.C > #include > #include > using namespace std; > > int main() { > try { >throw string("String"); > } catch (string s) { >

Re: C++ exceptions are broken in FreeBSD with gcc-compiled code?

On Wed, Apr 09, 2008 at 10:29:05AM -0700, Ted Faber wrote: > On Wed, Apr 09, 2008 at 09:39:09AM -0700, Yuri wrote: > > I am unable to make a C++ program to catch an exception using the the > > system g++ compiler. > > > > > cat exc.C > > #include > > #include > > using namespace std; > > > > i

Re: C++ exceptions are broken in FreeBSD with gcc-compiled code?

Erik Trulsson wrote: It works fine for me too, using FreeBSD 6-stable and the built-in gcc 3.4.6 as well as with gcc 4.2.4 20080305 installed from ports. No need to use -pthreads in either case This means that this issue is STABLE-7.0 specific. Yuri __

Re: C++ exceptions are broken in FreeBSD with gcc-compiled code?

On Wed, 09 Apr 2008 09:39:09 -0700 Yuri <[EMAIL PROTECTED]> wrote: > I am unable to make a C++ program to catch an exception using the the > system g++ compiler. % c++ -o exc exc.c % ./exc Caught an exception "String" % c++ -O2 -pthread -o exc exc.c % ./exc Caught an exc

RFC3514 for FreeBSD7

Hi! Well, i'm a bit late for this years aprils fools day, but the patch took much me longer than expected. Here it is, an updated and enhanced patch for RFC3514 "Security Flag in the IPv4 header", also known as the "evil bit". This patch now als

Re: C++ exceptions are broken in FreeBSD with gcc-compiled code?

> > It works fine for me too, using FreeBSD 6-stable and the built-in gcc > > 3.4.6 > > as well as with gcc 4.2.4 20080305 installed from ports. > > No need to use -pthreads in either case > > This means that this issue is STABLE-7.0 specific. I am not able to reproduce the problem here; I will

RFC3514 for FreeBSD7

Hi! Well, i'm a bit late for this years aprils fools day, but the patch took much me longer than expected. Here it is, an updated and enhanced patch for RFC3514 "Security Flag in the IPv4 header", also known as the "evil bit". This patch now also