On Wed, 2018-09-05 at 18:04 +0100, Richard W.M. Jones wrote: > On Wed, Sep 05, 2018 at 06:40:47PM +0200, Mark Wielaard wrote: > > We don't know the exact release version, but given the build-id > > [0aea4b30d53d7cc6386f1773a8dc8972793def1a] we should be able to > > match it against an older glibc package. > > Here are all the versions of glibc installed on that machine as far > back as the DNF logs go (which is only a couple of months > unfortunately): > > 2.26.9000-41.fc28 > 2.26.9000-48.fc28 > 2.27.9000-28.fc29 > 2.27.9000-35.fc29 > 2.28-6.fc29 > 2.28.9000-4.fc30 > 2.28-9.fc29 > > Of those only 2.27.9000-35.fc29 contains the build ID. > > That's the glibc-debuginfo that I already have installed (I realize > now why my previous email was wrong - the file is called > /usr/lib/debug/.build-id/0a/ea4b30d53d7cc6386f1773a8dc8972793def1a). > > However it still can't find a symbol matching the address, so I guess > we're out of luck. It might just be that the stack got corrupted, so the addresses don't really make sense. Note however that libc.so is a shared library that may be mapped everywhere. If you look at the partial backtrace that eu- stack generated you see: #0 0x00007f13c71ce46f - /usr/lib64/libc-2.27.9000.so (deleted) [0aea4b30d53d7cc6386f1773a8dc8972793def1a]@0x7f13c7197000+0x3746f #1 0x00007f13c72a4435 - 1 - /usr/lib64/libc-2.27.9000.so (deleted) [0aea4b30d53d7cc6386f1773a8dc8972793def1a]@0x7f13c7197000+0x10d434 Which says the file with build-id 0aea... was mapped at 0x7f13c7197000 so the offsets from the start of the mapping are 0x3746f and 0x10d434. Normally you would then try to match these against the .symtab in the .debug file. But glibc is special and keeps the symtab in the main file... So if you really want to hunt this down you might have to get the main glibc 2.27.9000-35.fc29 rpm and rpm2cpio it somewhere. Then try to extract the symbol table from that .../usr/lib64/libc-2.27.9000.so (eu- readelf -s). Or since you have the debugfile already try searching the .debuginfo with eu-readelf --debug-dump=info and look for a low_pc with 03746[a-f] to see if there is a construct that matches. Sorry this is all a bit messy (and possibly unresolvable if the stack was just corrupted). Cheers, Mark _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
