Philipp Kern schrieb am Mittwoch, den 02. November 2005: > Oh and please send me a the output of "bt full" in gdb. We recently > got a report[1] probably about the same problem and I need to know if > it crashes in the same component. Sure, here it is (I installed only debugging symbols for libstdc++ (let me know if you need more))
(gdb) bt full #0 0x0ef26eac in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #1 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #2 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #3 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #4 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #5 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #6 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #7 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 ---Type <return> to continue, or q <return> to quit--- No symbol table info available. #8 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. #9 0x0ef26e64 in __gnu_cxx::__pool<true>::_M_reclaim_block () from /usr/lib/libstdc++.so.6 No symbol table info available. (gdb) Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
