Core dump in bastring.cc

Manickam Palaniappan mpalania@cisco.com
Mon Mar 31 13:24:00 GMT 2003


Hi,
	There is some problem in basic_string during cleanup I presume. Am not 
using the up-to-date GCC release due to some constraints. Below is a core 
dump generated on calling exit(). Could anyone put some light on this?

Lock  class has a   private    "std::string name_ " member.

#0  0x25e9f5da in basic_string<char, string_char_traits<char>, 
__default_alloc_template<true, 0> >::~basic_string (this=0x80c6078,
     __in_chrg=2) at std/bastring.h:87
#1  0x25b439bb in Lock::~Lock (this=0x80c6078, __in_chrg=2) at /Lock.cpp:18
#2  0x806c303 in __static_initialization_and_destruction_0 
(__initialize_p=0, __priority=65535)
     at /Main.cpp:47
#3  0x806c365 in global destructors keyed to goDaemon () at /Main.cpp:88
#4  0x8069053 in __do_global_dtors_aux ()
     at 
/usr/local/gcc-2.95.2/lib/gcc-lib/i686-pc-linux-gnu/2.95.2/../../../../include/g++-3/std/bastring.cc:81
#5  0x809fe85 in _fini ()
#6  0x25f0925a in exit () from /lib/libc.so.6

Thanks,
Manickam

P.S:  tried getting a hand at the source but could not. FTP access asks for 
passwd. Where should I go for sources for this 2.95.2 release of g++.



More information about the Libstdc++ mailing list