Bug 157888 - Please make free() error backtraces read debuginfo
Please make free() error backtraces read debuginfo
Product: Fedora
Classification: Fedora
Component: glibc (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jakub Jelinek
Brian Brock
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-05-16 15:18 EDT by Robin Green
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-16 16:32:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robin Green 2005-05-16 15:18:18 EDT
Description of problem:
On detecting a double-free error, glibc prints a backtrace. (At least, I assume
it's glibc doing it.) But the backtrace does not give function names.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
0. Install firefox and firefox-debuginfo
1. firefox 'http://www.believermag.com/issues/200504/interview_mieville.php'
2. press the END key when page has loaded
Actual results:
glibc "double free or corruption" error on terminal, with a backtrace without
function names

Expected results:
The backtrace should be built using the installed debuginfo

Additional info:
Comment 1 Jakub Jelinek 2005-05-16 16:32:09 EDT
Doing that in glibc is a very bad idea, when memory is corrupted the program
should do as few things as possible and then terminate, otherwise it increases
risks of exploitation.
You can certainly run the addresses through trivial script to get the
addresses, but so can do whomever you report the problem to, assuming you
cut'n'paste the whole output glibc prints and
rpm -q --qf '%{name}-%{version}-%{release}.%{arch}\n' of relevant packages

Note You need to log in before you can comment on or make changes to this bug.