Hide Forgot
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): glibc-2.3.5-6 How reproducible: Always 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: firefox-1.0.4-2 firefox-debuginfo-1.0.4-2
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 installed.