On Mon, Oct 17, 2005 at 11:46:19PM +0200, Philipp Frauenfelder wrote: > 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. Two people have tried and failed to reproduce this problem on an up-to-date sid system. There is not enough information in this bug report to fix it without being able to reproduce it. If you have a valgrind report for this program, you may want to post it to the bug report. Likewise, a full backtrace may be a bit more helpful than just citing the innermost stack frame, which only tells us "something happened somewhere which abused the memory management interface". -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
