reopen 367030 found 367030 1:3.8.1-3 thanks On 2013-05-10 Alessandro Ghedini <[email protected]> wrote: > On ven, mag 12, 2006 at 03:16:13 -0700, Jason Spiro wrote: > > Package: valgrind > > Version: 1:3.1.1-1 [...] > > [snippety snip snip] > > > > --23346-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 > > (SIGSEGV) - exiting > > --23346-- si_code=1; Faulting address: 0x24930CD4; sp: 0x62416E50 > > > > valgrind: the 'impossible' happened: > > Killed by fatal signal
> Closing, since I can't reproduce this with a more recent valgrind. > Feel free to reopen if you can still reproduce this. Hello, I just got exactly the same mesage when trying get valgrind info for a failing test of gnutls28 on mips[1]: ---------------- (experimental_mips-dchroot)ametzler@gabrielli:~/GNUTLS$ valgrind ./gnutls28-3.1.11/tests/mini-xssl ==4877== Memcheck, a memory error detector ==4877== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al. ==4877== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==4877== Command: ./gnutls28-3.1.11/tests/mini-xssl ==4877== ==4877== Source and destination overlap in VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --4877-- si_code=1; Faulting address: 0xBB4C; sp: 0x426bdbd8 valgrind: the 'impossible' happened: Killed by fatal signal ==4877== at 0x380E6AB0: ??? (in /usr/lib/valgrind/memcheck-mips32-linux) ==4877== by 0x380E7584: ??? (in /usr/lib/valgrind/memcheck-mips32-linux) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==4877== at 0x484D4C4: memcpy (in /usr/lib/valgrind/vgpreload_memcheck-mips32-linux.so) ==4877== by 0x400ECD8: _dl_map_object_deps (dl-deps.c:657) ==4877== by 0x4028D24: ??? [...] ---------------- thanks, cu Andreas [1] http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/6745 -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
