tags 33407 + confirmed help thanks Am Mon, Oct 17, 2005 at 07:35:29PM +0200 hat Peter Henseler getippert: > after upgrading from version 0.1.2-6 gbib segfaults on program startup > and dumps a core file. The command: > gdb -c core `which gbib` > tells me: > #0 0x0f77bfa0 in __gnu_cxx::__pool<true>::_M_reclaim_block () from > /usr/lib/libstdc++.so.6 > I hope, this helps to locate the bug. > > So long, the problem can be circumvented by downgrading to the former > version 0.1.2-6.
Same on i386. Sorry, I have no quick idea what went wrong. However, running gbib under valgrind (only for i386 and amd64), I get a lot of errors and a working gbib. This usually indicates that an array bound overwrite takes place which is caught by valgrind and does not do any harm anymore. Without valgrind, the array bound overwrite destroys something which leads to the error. The version -6 was compiled with a former compiler which did not provoke the problem. Due to real world problems, I do not have the time to fix this in the near future. Upstream has similar problems. :-( Regards -- Philipp | work: [EMAIL PROTECTED] +41 1 802 20 00 Frauenfelder | home: [EMAIL PROTECTED] +41 1 862 73 14 [PGP] | http://www.frauenfelder-kuerner.ch/ Proudly running Debian GNU/Linux. See http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
