Your message dated Tue, 7 Feb 2017 17:20:44 +0800 with message-id <CAKcpw6WTY5zdpPXYJcFMxOmhe9Sr5JZTu3=O1=wt--tgrxk...@mail.gmail.com> and subject line Re: valgrind segfaults on mipsel has caused the Debian Bug report #854194, regarding valgrind segfaults on mipsel to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 854194: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: valgrind Version: 1:3.12.0~svn20160714-1+b1 Severity: serious Seen with both 1:3.12.0~svn20160714-1+b1 and 1:3.12.0-1.1: (sid_mipsel-dchroot)bunk@eller:~$ valgrind /usr/bin/hello ==32333== Memcheck, a memory error detector ==32333== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==32333== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==32333== Command: /usr/bin/hello ==32333== Segmentation fault (sid_mipsel-dchroot)bunk@eller:~$ gdb /usr/bin/valgrind.bin GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "mipsel-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/bin/valgrind.bin...Reading symbols from /usr/lib/debug//usr/bin/valgrind.bin...done. done. (gdb) run /usr/bin/hello Starting program: /usr/bin/valgrind.bin /usr/bin/hello process 32540 is executing new program: /usr/lib/valgrind/memcheck-mips32-linux ==32540== Memcheck, a memory error detector ==32540== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==32540== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==32540== Command: /usr/bin/hello ==32540== warning: GDB can't find the start of the function at 0x433a2f74. GDB is unable to find the start of the function at 0x433a2f74 and thus can't determine the size of that function's stack frame. This means that GDB may be unable to access that stack frame, or the frames below it. This problem is most likely caused by an invalid program counter or stack pointer. However, if you think GDB should simply search farther back from 0x433a2f74 for code which looks like the beginning of a function, you can increase the range of the search using the `set heuristic-fence-post' command. Program received signal SIGSEGV, Segmentation fault. 0x433a2f74 in ?? () (gdb)
--- End Message ---
--- Begin Message ---On Sun, 05 Feb 2017 00:39:49 +0200 Adrian Bunk <b...@debian.org> wrote: > Package: valgrind > Version: 1:3.12.0~svn20160714-1+b1 > Severity: serious > It seems that 1:3.12.0-1.1 doesn't have this problem. I also test it on Loongson 3A. root@thor:/# valgrind /usr/bin/hello ==2085== Memcheck, a memory error detector ==2085== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==2085== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==2085== Command: /usr/bin/hello ==2085== VEX: Unsupported baseline Found: Loongson-baseline Cannot continue. Good-bye vex storage: T total 0 bytes allocated vex storage: P total 0 bytes allocated valgrind: the 'impossible' happened: LibVEX called failure_exit(). host stacktrace: ==2085== at 0x38086EFC: show_sched_status_wrk (m_libcassert.c:343) ==2085== by 0x380870C8: report_and_quit (m_libcassert.c:419) ==2085== by 0x38087338: panic (m_libcassert.c:495) ==2085== by 0x38087338: vgPlain_core_panic_at (m_libcassert.c:500) ==2085== by 0x3808737C: vgPlain_core_panic (m_libcassert.c:505) ==2085== by 0x380AAC9C: failure_exit (m_translate.c:740) ==2085== by 0x3818D5E4: vfatal (main_util.c:552) ==2085== by 0x38189AF8: invalid_hwcaps (main_main.c:1789) ==2085== by 0x38189DC0: check_hwcaps (main_main.c:1991) ==2085== by 0x3818A63C: LibVEX_Translate (main_main.c:592) ==2085== by 0x380ADE8C: vgPlain_translate (m_translate.c:1770) ==2085== by 0x380F3F60: handle_tt_miss (scheduler.c:1048) ==2085== by 0x380F3F60: vgPlain_scheduler (scheduler.c:1409) ==2085== by 0x38109CC0: thread_wrapper (syswrap-linux.c:103) ==2085== by 0x38109CC0: run_a_thread_NORETURN (syswrap-linux.c:156) ==2085== by 0x3810A54C: vgPlain_main_thread_wrapper_NORETURN (syswrap-linux.c:417) sched status: running_tid=1 Thread 1: status = VgTs_Runnable (lwpid 2085) ==2085== at 0x4000D00: __start (in /lib/mipsel-linux-gnu/ld-2.24.so) ==2085== by 0x7EBBF648: ??? 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. > Seen with both 1:3.12.0~svn20160714-1+b1 and 1:3.12.0-1.1: > > (sid_mipsel-dchroot)bunk@eller:~$ valgrind /usr/bin/hello > ==32333== Memcheck, a memory error detector > ==32333== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. > ==32333== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info > ==32333== Command: /usr/bin/hello > ==32333== > Segmentation fault > (sid_mipsel-dchroot)bunk@eller:~$ gdb /usr/bin/valgrind.bin > GNU gdb (Debian 7.12-6) 7.12.0.20161007-git > Copyright (C) 2016 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "mipsel-linux-gnu". > Type "show configuration" for configuration details. > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>. > Find the GDB manual and other documentation resources online at: > <http://www.gnu.org/software/gdb/documentation/>. > For help, type "help". > Type "apropos word" to search for commands related to "word"... > Reading symbols from /usr/bin/valgrind.bin...Reading symbols from > /usr/lib/debug//usr/bin/valgrind.bin...done. > done. > (gdb) run /usr/bin/hello > Starting program: /usr/bin/valgrind.bin /usr/bin/hello > process 32540 is executing new program: > /usr/lib/valgrind/memcheck-mips32-linux > ==32540== Memcheck, a memory error detector > ==32540== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. > ==32540== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info > ==32540== Command: /usr/bin/hello > ==32540== > warning: GDB can't find the start of the function at 0x433a2f74. > > GDB is unable to find the start of the function at 0x433a2f74 > and thus can't determine the size of that function's stack frame. > This means that GDB may be unable to access that stack frame, or > the frames below it. > This problem is most likely caused by an invalid program counter or > stack pointer. > However, if you think GDB should simply search farther back > from 0x433a2f74 for code which looks like the beginning of a > function, you can increase the range of the search using the `set > heuristic-fence-post' command. > > Program received signal SIGSEGV, Segmentation fault. > 0x433a2f74 in ?? () > (gdb) > >
--- End Message ---
