Bug 560626
| Summary: | abrt reports valgrind as crashing program | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Nečas <yeti> |
| Component: | abrt | Assignee: | Jiri Moskovcak <jmoskovc> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | anton, dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, mnowak, npajkovs |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | 1.0.6-1.fc12 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-02-09 21:03:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Valgrind was added to abrt's blacklist in 1.0.5, so it will ignore such crashes. Jirka valgrind indeed kills itself with SIGSEGV in this case: $ strace -oLOG valgrind ./unknown ... kill(2988, SIGSEGV) = 0 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ I see. If killing itself with SIGSEGV is the `normal' behaviour then blacklisting by default is probably the only reasonable option. abrt-1.0.6-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.0.6-1.fc12 abrt-1.0.6-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1470 abrt-1.0.6-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: Running a segfaulting program under valgrind causes abrt to show valgrind as the crashing program. This is not a big problem but it's definitely annoying. If you are root, you can blacklist valgrind to stop this. Perhaps valgrind should be blacklisted by default if there is not reasonable way to detect this situation? Version-Release number of selected component (if applicable): abrt-1.0.4-1.fc12.x86_64 How reproducible: Always. Steps to Reproduce: 1. gcc -xc -o unknown - <<<'main(){*(int*)0=1;}' 2. valgrind ./unknown Actual results: ==16373== Memcheck, a memory error detector ==16373== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==16373== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info ==16373== Command: ./unknown ==16373== ... ==16373== ... ==16373== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 6 from 6) Segmentation fault (core dumped) Then vgcore.12345 is dumped (does not depend on MakeCompatCore, good) and abrt's blinking beacon appears in GNOME, reporting the crash as valgrind's crash. Expected results: The same except the blinking beacon part, i.e. the crash is handled as a crash of an unknown program, not valgrind's. Additional info: