[Bug general/5620] RHEL 5.2 occasional backtraces resolve libc as unknown

["pmuldoon at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From pmuldoon at redhat dot com  2008-01-16 21:42 -------
After analysis I believe this is the issue:

Occasionally the vdso gets relocated to a location that libc occupies. This
causes the libc libraries to be relocated, and causing the [unknown] library in
the backtrace.  This really designates an unrelocated libc bug. Or in fact, any
solib relocation bug.

In the linkmap table there is a l_addr field which designates absolute location
of a map in memory. In practice this should equal to the l_addr + virt start
address of the LOAD statement of the solib in question. This relocation is not
being taken into account in corefile modeling. It seems a rare occasion. At best
it seems it only occurs when the vdso is located where an solib should live, and
the solib is shifted.

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=5620

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.