Re: agh! lots of problems with libc6 v2.3.5-6 (x86) and libc6-dbg
On Mon, Oct 03, 2005 at 04:15:40PM +0100, Nic Ferrier wrote:
> > What does the backtrace look like without libc6-dbg installed? What
> > does it look like with?
>
> It's got all the steps in it:
>
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> [New Thread 1075424928 (LWP 25289)]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> <libxslt.stylesheet instance at 0x4020012c>
>
> As you can see, not much use.
That's not a backtrace. I mean the actual output of "backtrace"...
> Before I installed libc6-dbg I could see which part of Python or
> libxml2 these calls were coming from.
>
> I can't get that information back however, even if I uninstall
> libc6-dbg. I tried removing libc6-dbg and then reinstalling libc6 but
> to no avail.
Then I'm afraid it's something unrelated to glibc in your environment,
and we can't help you.
--
Daniel Jacobowitz
CodeSourcery, LLC
Reply to: