This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
shlibs/1777: Warning with core file generated on Suse 9.1 (glibc 2.3.3)
- From: jcownie at etnus dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 16 Sep 2004 10:35:43 -0000
- Subject: shlibs/1777: Warning with core file generated on Suse 9.1 (glibc 2.3.3)
- Reply-to: jcownie at etnus dot com
>Number: 1777
>Category: shlibs
>Synopsis: Warning with core file generated on Suse 9.1 (glibc 2.3.3)
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: external
>Submitter-Id: net
>Arrival-Date: Thu Sep 16 10:38:01 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: jcownie@etnus.com
>Release: GNU gdb 6.1
>Organization:
>Environment:
This GDB was configured as "x86_64-suse-linux".
(Though I'm debugging a 32 bit image and core file).
>Description:
A bug in glibc http://sources.redhat.com/bugzilla/show_bug.cgi?id=387
causes gdb to fail to be able to locate the dynamic linker
when debgging core files on Suse 9.1 (at least).
gdb issues the message
warning: current_sos: Can't read pathname for load map: Input/output error
I'm logging this here as well as with the glibc folks since
I think gdb maintainers should know about it (since it's
gdb which prints the message), and I'd like your support in
getting the glibc maintainers to fix it the right way
(get the filename back into the core file), rather than
saying that there's some other way (maybe via the auxv) to
find the name of the dynamic linker and that we should
be adding yet more complexity to the debugger to work
around their bug :-)
>How-To-Repeat:
Try to debug a core file on Suse 9.1
>Fix:
ld-linux.so needs to be fixed.
>Release-Note:
>Audit-Trail:
>Unformatted: