Public bug reported:
Binary package hint: valgrind
$ lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
$ apt-cache policy valgrind
valgrind:
Installiert: 1:3.6.0~svn20100212-0ubuntu5
Kandidat: 1:3.6.0~svn20100212-0ubuntu5
Versions-Tabelle:
*** 1:3.6.0~svn20100212-0ubuntu5 0
500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ lucid/main
Packages
100 /var/lib/dpkg/status
I expected valgrind shows the root cause of my segmentation fault.
Instead the impossible happened:
$ valgrind ./hello_world
==17537== Memcheck, a memory error detector
==17537== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==17537== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for
copyright info
==17537== Command: ./hello_world
==17537==
--17537-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) -
exiting
--17537-- si_code=1; Faulting address: 0x8525B1EC; sp: 0x403187150
valgrind: the 'impossible' happened:
Killed by fatal signal
==17537== at 0x38054D18: read_elf_symtab__normal (readelf.c:360)
==17537== by 0x38058112: vgModuleLocal_read_elf_debug_info (readelf.c:2065)
==17537== by 0x38053AE9: vgPlain_di_notify_mmap (debuginfo.c:818)
==17537== by 0x38070C69: vgModuleLocal_generic_PRE_sys_mmap
(syswrap-generic.c:2039)
==17537== by 0x38091DB9: vgSysWrap_amd64_linux_sys_mmap_before
(syswrap-amd64-linux.c:984)
==17537== by 0x380674D7: vgPlain_client_syscall (syswrap-main.c:1442)
==17537== by 0x3806406D: handle_syscall (scheduler.c:885)
==17537== by 0x38064EC9: vgPlain_scheduler (scheduler.c:1081)
==17537== by 0x3808E444: run_a_thread_NORETURN (syswrap-linux.c:91)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable
==17537== at 0x4017CDA: mmap (syscall-template.S:82)
==17537== by 0x4006936: _dl_map_object_from_fd (dl-load.c:1246)
==17537== by 0x40088AF: _dl_map_object (dl-load.c:2234)
==17537== by 0x400C95C: openaux (dl-deps.c:65)
==17537== by 0x400E8C5: _dl_catch_error (dl-error.c:178)
==17537== by 0x400D053: _dl_map_object_deps (dl-deps.c:247)
==17537== by 0x40037CF: dl_main (rtld.c:1782)
==17537== by 0x40165C6: _dl_sysdep_start (dl-sysdep.c:243)
==17537== by 0x4001386: _dl_start (rtld.c:333)
==17537== by 0x4000AF7: ??? (in /lib/ld-2.11.1.so)
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
** Affects: valgrind (Ubuntu)
Importance: Undecided
Status: New
--
the 'impossible' happened: Killed by fatal signal
https://bugs.launchpad.net/bugs/681823
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
