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.
Created attachment 387108 [details] File: backtrace
This is a crash in whatever program you were analyzing using valgrind, not valgrind itself.