gcc 2.96, libstdc++ v3 and efence

Maurizio Umberto Puxeddu umbpux@tin.it
Mon Aug 21 03:56:00 GMT 2000


This simple code segfaults if compiled with CVS GCC 2.96 using libstdc++
v3 and linked to efence:

#include <stdlib.h>


  char *p = (char *)malloc(100);

  return 0;

This is the stack trace:

Program received signal SIGSEGV, Segmentation fault.
std::ios_base::~ios_base (this=0x400e9184, __in_chrg=0)
    at ../../../../gcc/libstdc++-v3/bits/localefwd.h:344
344           if (_M_num_references-- == 0)  // XXX MT
(gdb) bt
#0  std::ios_base::~ios_base (this=0x400e9184, __in_chrg=0)
    at ../../../../gcc/libstdc++-v3/bits/localefwd.h:344
#1  0x400782d7 in __static_initialization_and_destruction_0
    __priority=65535) at
#2  0x400785c2 in global destructors keyed to std::__cfileinit ()
    at ../../../../gcc/libstdc++-v3/bits/std_fstream.h:96
#3  0x40066d2d in __do_global_dtors_aux () from
#4  0x400ce5e9 in ?? () from /usr/local2/lib/libstdc++.so.3
#5  0x4000aef6 in _dl_fini () at dl-fini.c:40
#6  0x4012825a in exit (status=0) at exit.c:57
#7  0x4011f9d1 in __libc_start_main () at

As far as I can understand this is a standard library problem (I posted
to gcc-help too just because I'm using the stdc++ library from the GCC
The same code runs fine with the stock RH Linux 6.2 GCC.
(I checked out GCC last week. Now I'm updating my sources and compiling
it again)
Is it a bug?

Maurizio Umberto Puxeddu

More information about the Libstdc++ mailing list