On Fri, Sep 30, 2005 at 09:11:09PM +0100, Nic Ferrier wrote: > I just upped my testing version of libc (I've now got 2.3.5-6) and I'm > having a few problems... unfortunately, I'm also having a few problems > debugging. > > I've got a python/libxml2/libxslt app that now reports: > > *** glibc detected *** double free or corruption (fasttop): 0x081be648 *** > > when I call a particular libxslt method more than once. > > So, to try to find out whether this is a libc bug (looked like it > might be to me) I tried debugging the python: > > gdb python > => run testxsl.py > > that showed me the stack trace of what was at fault. I got a good list > with all the symbols from inside python and from inside the > libxml2/libxslt libraries. > > Unfortunately, I was then stupid and installed libc6-dbg in order to > get more info. > > Now I get *no* python or libxml2/libxslt symbols in the stack > traces.
What does the backtrace look like without libc6-dbg installed? What does it look like with? -- Daniel Jacobowitz CodeSourcery, LLC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
