I'm working on `RHEL WS 4.5`.

I've obtained the glibc source rpm matching this system, opened it to get its contents using rpm2cpio.

Working in that tree, I've created a patch to mtrace.c (i want to add more stack backtrace levels) and incorporated it in the spec file and created a new set of RPMs including the debuginfo rpms.

I installed all of these on a test vm (created from the same RH base image) and can confirm that my changes are included.

But with more complex executions, I crash in mtrace.c ... but gdb can't find the debug information so I don't get line number info and I can't actually debug the failure.

Based on dates, I think I can confirm that the debug information is installed on the test system in /usr/src/debug/glibc-2.3.6/

I tried 
 `sharedlibrary libc*`
in gdb and it tells me the symbols are already loaded.

My test includes a locally built python and full symbols are found for python.

My sense is that perhaps glibc isn't being built under rpmbuild with debug enabled. I've reviewed the glibc.spec file and even built with

\_enable\_debug\_packages

defined as 1 which looked like it might influence the result. My review of the configure scripts invoked during the rpmbuild build step didn't give me any hints.

Hmmmm .. just found /usr/lib/debug/lib/libc-2.3.4.so.debug
and /usr/lib/debug/lib/tls/i486/libc-2.3.4.so.debug
but both of these are reported as stripped by the file command.