------- Comment #5 from sebor at roguewave dot com 2006-12-22 22:25 ------- Regardless of whether the program aborts with SIGSEGV or SIGABRT, the point is that it should either not compile or it should run succesfully to completion.
Here's the output of g++ -v if it helps: $ g++ -v Using built-in specs. Target: sparc-sun-solaris2.9 Configured with: /build/sebor/gcc-4.1.0/configure --enable-languages=c,c++ --prefix=/usr/local/gcc-4.1.0 : (reconfigured) /build/sebor/gcc-4.1.0/configure --enable-languages=c,c++ --prefix=/usr/local/gcc-4.1.0 : (reconfigured) /build/sebor/gcc-4.1.0/configure --enable-languages=c,c++ --prefix=/usr/local/gcc-4.1.0 --with-gnu-as --with-gnu-ld Thread model: posix gcc version 4.1.0 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30280
