Bug 562526 - [abrt] crash in valgrind-1:3.5.0-14.fc12
Summary: [abrt] crash in valgrind-1:3.5.0-14.fc12
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: valgrind
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:59d5aee564a776199a5be220fd7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-07 08:53 UTC by Eduardo Tapia
Modified: 2010-02-08 08:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-08 08:44:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (1.94 KB, text/plain)
2010-02-07 08:53 UTC, Eduardo Tapia
no flags Details

Description Eduardo Tapia 2010-02-07 08:53:05 UTC
abrt 1.0.4 detected a crash.

architecture: x86_64
cmdline: valgrind --leak-check=full --undef-value-errors=no --show-reachable=yes ./sslclient
component: valgrind
executable: /usr/lib64/valgrind/memcheck-amd64-linux
kernel: 2.6.31.12-174.2.3.fc12.x86_64
package: valgrind-1:3.5.0-14.fc12
rating: 3
reason: Process was terminated by signal 6 (Aborted)
release: Fedora release 12 (Constantine)

backtrace
-----
warning: core file may not match specified executable file.
Core was generated by `valgrind --leak-check=full --undef-value-errors=no --show-reachable=yes ./sslcl'.
Program terminated with signal 6, Aborted.
#0  0x000000003803da19 in do_syscall_WRK ()

Thread 1 (Thread 6504):
#0  0x000000003803da19 in do_syscall_WRK ()
No locals.
#1  0x000000003803dba2 in vgPlain_do_syscall (sysno=<value optimized out>, 
    a1=<value optimized out>, a2=<value optimized out>, 
    a3=<value optimized out>, a4=<value optimized out>, 
    a5=<value optimized out>, a6=<value optimized out>, 
    a7=<value optimized out>, a8=<value optimized out>) at m_syscall.c:702
        val = <value optimized out>
#2  0x000000003802dee6 in vgPlain_kill (pid=<value optimized out>, 
    signo=<value optimized out>) at m_libcsignal.c:304
        res = {_val = 0, _isError = 0 '\000'}
#3  0x000000003803c012 in vgPlain_kill_self (sigNo=6) at m_signals.c:1353
        mask = {sig = {32}}
        origmask = {sig = {18446744073709287975}}
        sa = {ksa_handler = 0, sa_flags = 0, sa_restorer = 0, sa_mask = {
            sig = {0}}}
        origsa2 = {ksa_handler = 0, sa_flags = 8589934592, 
          sa_restorer = 0x402042cb0, sa_mask = {sig = {939756032}}}
        origsa = {ksa_handler = 0x3803b860 <async_signalhandler>, 
          sa_flags = 335544324, sa_restorer = 0x3803a4d0 <my_sigreturn>, 
          sa_mask = {sig = {18446744073709289215}}}
#4  0x000000003803333d in shutdown_actions_NORETURN (
    tid=<value optimized out>, tids_schedretcode=VgSrc_FatalSig)
    at m_main.c:2495
        __PRETTY_FUNCTION__ = "shutdown_actions_NORETURN"
#5  0x000000003808bd3c in run_a_thread_NORETURN (tidW=1)
    at m_syswrap/syswrap-linux.c:146
        tid = 1
        src = VgSrc_FatalSig
        c = 1
        __PRETTY_FUNCTION__ = "run_a_thread_NORETURN"
#6  0x0000000000000000 in ?? ()
No symbol table info available.
No shared libraries loaded at this time.
No symbol "__abort_msg" in current context.

Comment 1 Eduardo Tapia 2010-02-07 08:53:09 UTC
Created attachment 389350 [details]
File: backtrace

Comment 2 Jakub Jelinek 2010-02-08 08:44:07 UTC
This is an abrt issue, it shouldn't report valgrind crashes against valgrind, because when valgrind aborts, it means it found a fatal bug in the application it is tracing.


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