This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Need help to fill bug report (gcc 4.0.1 and above)
- From: Mathieu Malaterre <mathieu dot malaterre at kitware dot com>
- To: gcc at gcc dot gnu dot org
- Date: Sun, 28 Aug 2005 09:51:06 -0400
- Subject: Need help to fill bug report (gcc 4.0.1 and above)
Hello,
I have currently a reproducable seg fault from an exe produced by gcc
4.0.1 (*). It does not appear using gcc 2.95, 3.2, 3.3, 3.4.
If I run it throught gdb I get:
0x402814b1 in __gnu_cxx::__pool<true>::_M_reclaim_block () from
/usr/lib/libstdc++.so.6
(gdb) bt
#0 0x402814b1 in __gnu_cxx::__pool<true>::_M_reclaim_block () from
/usr/lib/libstdc++.so.6
#1 0x08062907 in
__gnu_cxx::__mt_alloc<std::_Rb_tree_node<std::pair<std::string,
std::string> >, __gnu_cxx::__common_pool_policy<__gnu_cxx::__pool, true>
>::deallocate (this=0x806d888, __p=0x8221f10, __n=1) at mt_allocator.h:746
...
and the structure being:
static std::set< std::pair< std::string, std::string > > foo;
If I try to run through valgrind 3.0 everything is fine, and it produce
correct output.
Any advice on a way to narrow down a simple testcase, right now it would
require building VTK(**)
Thanks for any help,
Mathieu
(*) debian testing. but I can also reproduce with gcc 4.1.0 20050726
(gcc-snapshot)
(**) http://vtk.org