[Bug libc/387] New: ld-linux.so has its name in ro_data in link_map entry => problem in core files

["jcownie at etnus dot com" <sourceware-bugzilla at sources dot redhat dot com>]

The dynamic linker ld-linux.so.2 is using a string in its .ro_data segment
as the target of the struct link_map entry which describes it.

This means that when core is dumped this name string is not in the core file 
(since only writeable segments are dumped).

When a core analysis tool (such as gdb) tries to interpret the chain of
link_map entries from the core file to determine which dynamic libraries
were loaded it has a bootstrap problem. The name of the dynamic linker's file
is in the file itself, and not in the core file.

In previous releases this name was not in the .ro_data segment, and therefore
was dumped to the core file avoiding the problem.

The proximate syptom is the message 

   warning: current_sos: Can't read pathname for load map: Input/output error

from gdb when trying to debug a core file, however the cause
is the change in the dynamic linker which has removed necessary information
from the core file.

-- 
           Summary: ld-linux.so has its name in ro_data in link_map entry =>
                    problem in core files
           Product: glibc
           Version: 2.3.3
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: gotom at debian dot or dot jp
        ReportedBy: jcownie at etnus dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i686-suse-linux
  GCC host triplet: i686-suse-linux
GCC target triplet: i686-suse-linux


http://sources.redhat.com/bugzilla/show_bug.cgi?id=387

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.