Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 157888 - Please make free() error backtraces read debuginfo
Summary: Please make free() error backtraces read debuginfo
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-05-16 19:18 UTC by Robin Green
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2005-05-16 20:32:09 UTC

Attachments (Terms of Use)

Description Robin Green 2005-05-16 19:18:18 UTC
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 ''
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 20:32:09 UTC
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.