Bug 560626 - abrt reports valgrind as crashing program
Summary: abrt reports valgrind as crashing program
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: abrt
Version: 12
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jiri Moskovcak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-01 12:45 UTC by David Nečas
Modified: 2015-02-01 22:50 UTC (History)
8 users (show)

Fixed In Version: 1.0.6-1.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-09 21:03:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Nečas 2010-02-01 12:45:38 UTC
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:

Comment 1 Jiri Moskovcak 2010-02-01 12:52:17 UTC
Valgrind was added to abrt's blacklist in 1.0.5, so it will ignore such crashes.

Jirka

Comment 2 Denys Vlasenko 2010-02-01 13:03:53 UTC
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 +++

Comment 3 David Nečas 2010-02-01 13:19:51 UTC
I see.  If killing itself with SIGSEGV is the `normal' behaviour then blacklisting by default is probably the only reasonable option.

Comment 4 Fedora Update System 2010-02-03 15:18:08 UTC
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

Comment 5 Fedora Update System 2010-02-05 01:32:29 UTC
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

Comment 6 Fedora Update System 2010-02-09 21:02:35 UTC
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.


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