Bug 550559 - [abrt] crash detected in elfutils-0.143-1.fc12
[abrt] crash detected in elfutils-0.143-1.fc12
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: elfutils (Show other bugs)
12
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Roland McGrath
Fedora Extras Quality Assurance
abrt_hash:e52fc101bfb0afbf0b3e0458ba1...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-12-25 20:36 EST by Andre Cruz
Modified: 2010-03-11 08:55 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-03-11 08:55:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
File: backtrace (3.00 KB, text/plain)
2009-12-25 20:36 EST, Andre Cruz
no flags Details

  None (edit)
Description Andre Cruz 2009-12-25 20:36:37 EST
abrt 1.0.0 detected a crash.

Attached file: backtrace
cmdline: eu-unstrip --core=/var/cache/abrt/ccpp-1261188844-2625/coredump -n
component: elfutils
executable: /usr/bin/eu-unstrip
kernel: 2.6.31.6-166.fc12.i686
package: elfutils-0.143-1.fc12
rating: 4
reason: Process was terminated by signal 11
Comment 1 Andre Cruz 2009-12-25 20:36:40 EST
Created attachment 380378 [details]
File: backtrace
Comment 2 Roland McGrath 2010-03-11 03:37:44 EST
You have reported a bug via the abrt daemon because the eu-unstrip utility crashed.  You did not use eu-unstrip yourself, but instead some other application you were using crashed and the abrt daemon caught that crash and tried to examine the coredump file.  abrt ran eu-unstrip on this saved coredump file, and that's when eu-unstrip crashed.  We have fixed some bugs that explain some crashes of this sort, but we can't be entirely sure that we've fixed what bit you unless you can reproduce it and test it for us.  We have no idea what the original application you were running was--you might be able to tell with "file" or "eu-readelf -n" on the coredump file if you still have it--but we don't really care, we just want that coredump file as a test case for the eu-unstrip problem.

Please look at the "cmdline:" line in comment#0 and try repeating this command.  It's possible you'll need to be root to be allowed to see that file (I'm not sure about this).  If you get a permission error, then I would recommend that you use sudo or su to cp that /var/cache/abrt/... file from comment#0 to another place, say /tmp/coredump, and also do "chmod a+r /tmp/coredump" (with su or sudo).  Then repeat the eu-unstrip command as a non-root user, but replacing the original file name with /tmp/coredump.

If you get an error because you no longer have this file at all, then there is nothing either of us can do to investigate your bug any more.  Please just close this report.

If the eu-unstrip command completes successfully without crashing (it will emit a bunch of lines of mostly hex and some strings similar to file names), then please double-check that you have the same exact elfutils rpm installed now that the comment#0 report said, and try it again.  If it still succeeds, then we probably are not going to be able to figure out how it crashed the first time.  If you really want to pursue it, then talk to the abrt folks on the crash-catcher@lists.fedorahosted.org mailing list and work out how to recreate the circumstances of the crashing eu-unstrip run.  If you don't care that much (I wouldn't), or that doesn't get anywhere, then tough luck and please just close this report.

If the eu-unstrip command dies with an error message or a signal, then try updating with yum or PackageKit to get the 0.145-1 version of elfutils.  Then try the command again.  If it still fails, in the same or different ways, then please follow up here with those details, and if you can (and it doesn't include any private information), make that coredump file available to us (preferably heavily compressed) via a web site or a bugzilla attachment if the compressed coredump file is not too huge.  Then we'll try to reproduce it ourselves with 0.145-1.

If 0.145-1 fixes your problem after you reproduced it, then please close this report, and you can set the "Fixed in version" field to be really nice about it.

If you don't care enough to follow up on any of that, then please just close this report.  Thanks for reporting your bugs to Fedora.
Comment 3 Andre Cruz 2010-03-11 08:55:16 EST
Roland, I'm sorry but I don't have the coredump anymore. I hope that the problem is reported by other users and you can identify the root cause. Thank you for your help and congratulations by Fedora SO.

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