[Bug threads/28014] gdb coredumps when remote+kgdbing a system that OOMs too hard

["rincebrain at gmail dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=28014

--- Comment #6 from Rich <rincebrain at gmail dot com> ---
(In reply to Simon Marchi from comment #5)
> It dug a little bit.  I checked why GDB couldn't see any shared library, I
> think there's a little bug in the MIPS-specific code where GDB uses a
> MIPS-specific auxv entry to locate the base of the runtime loader.  It
> doesn't take into account the main executable's runtime address.

Lovely.

> To get further, we would need libc's debug info.  I tried to find debug info
> for libc.so.6 but can't find it.  It's supposed to be in the libc6 package,
> which I think should be found here:
> 
> http://debug.mirrors.debian.org/debian-debug/pool/main/g/glibc/
> 
> But I can't find the debug package corresponding to
> libc6_2.31-12_mips64el.deb. The libc's build-id is
> 59aa6ff984aff00883acda7feef7613cce475991, I can't find that in any of the
> packages.  Do you have an idea?

I think you're getting burned because glibc is one of the ones that (for legacy
reasons, now that $RELEASE-debug is a thing? I'm unsure.) gets shoved in a -dbg
package in the main repos. gdb finds those symbols and loads them for me, even
as everything else horfs; I haven't tried recompiling gdb with that patch,
though.

-- 
You are receiving this mail because:
You are on the CC list for the bug.