Bug 559264

Summary: [abrt] crash in valgrind-1:3.5.0-14.fc12
Product: [Fedora] Fedora Reporter: apogi <apogi.muller>
Component: valgrindAssignee: Jakub Jelinek <jakub>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dodji, jakub
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:a1741d646101aeebd40bfb127a9b53dc21c8c891
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-01-28 09:30:07 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:
Attachments:
Description Flags
File: backtrace none

Description apogi 2010-01-27 15:43:25 UTC
abrt 1.0.4 detected a crash.

architecture: i686
cmdline: valgrind -q --log-file=/home/apogi/.valgrind-session/vgout.%p --error-limit=no --trace-children=yes --alignment=8 --num-callers=32 --undef-value-errors=no --leak-check=yes --show-reachable=no --leak-resolution=high /usr/bin/gnome-panel
component: valgrind
executable: /usr/lib/valgrind/memcheck-x86-linux
kernel: 2.6.31.12-174.2.3.fc12.i686
package: valgrind-1:3.5.0-14.fc12
rating: 3
reason: Process was terminated by signal 11 (Segmentation fault)
release: Fedora release 12 (Constantine)

backtrace
-----
warning: core file may not match specified executable file.
Core was generated by `valgrind -q --log-file=/home/apogi/.valgrind-session/vgout.%p --error-limit=no'.
Program terminated with signal 11, Segmentation fault.
#0  0x3803c302 in do_syscall_WRK ()

Thread 1 (Thread 1949):
#0  0x3803c302 in do_syscall_WRK ()
No symbol table info available.
No shared libraries loaded at this time.
No symbol "__abort_msg" in current context.

Comment 1 apogi 2010-01-27 15:43:27 UTC
Created attachment 387108 [details]
File: backtrace

Comment 2 Jakub Jelinek 2010-01-28 09:30:07 UTC
This is a crash in whatever program you were analyzing using valgrind, not valgrind itself.