[ Reported to the Debian BTS as report #169862. Please CC 169862@bugs.debian.org on replies. Log of report can be found at http://bugs.debian.org/169862 ] rechecked with 3.2 branch 20021220 and 3.3 branch 20021227 Not sure if this is a problem with the CPU, the kernel, the compiler, or the library. But this seems the most likely candidate. Consider the sample program below. When compiled as g++ foo.cc -ftrapv -o foo and run, the resultant binary immediately aborts. #include <vector> using namespace std; typedef vector<int> foo_t; int main() { vector<foo_t> V(10, foo_t()); return 0; } Release: 3.2.1 (Debian) (Debian unstable) Environment: System: Debian GNU/Linux (unstable) Architecture: i686 host: i386-linux configured with: /mnt/data/gcc-3.1/gcc-3.1-3.1ds2/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=$\(prefix\)/share/man --infodir=$\(prefix\)/share/info --with-gxx-include-dir=$\(prefix\)/include/g++-v3-3.1 --enable-shared --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --enable-clocale=gnu --enable-threads=posix --enable-java-gc=boehm --enable-objc-gc i386-linux
State-Changed-From-To: open->analyzed State-Changed-Why: Confirmed. Seems related to libstdc++/1823, which I can also reproduce with gcc3.2.1 (glibc2.3.1, i686-pc-linux-gnu)
*** This bug has been marked as a duplicate of 1823 ***