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. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]
