memcheck-amd64-linux crashed with SIGILL during valgrind --leak-check of my binary

Bug #1765001 reported by Thomas A. F. Thorne
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Valgrind
Unknown
Unknown
valgrind (Ubuntu)
New
Undecided
Unassigned

Bug Description

On Ubuntu 16.04 I ran a
valgrind --leak-check=yes -v
against a debug binary I had compiled using g++ (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609.

When I run without the -v option there is no crash reported. With the -v option I have generated a bug prompt 2 runs for 2 (the first time I had out of date packaged though).

#136538 was suggested as a possible, and it could be that but as it was a long time ago I made a new one. That itself says it could be #97531 but that claims to now no longer be an issue.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: valgrind 1:3.11.0-1ubuntu4.2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Wed Apr 18 10:47:40 2018
ExecutablePath: /usr/lib/valgrind/memcheck-amd64-linux
InstallationDate: Installed on 2017-11-16 (152 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/bin/valgrind.bin --leak-check=yes -v ./dmcp-debug
Signal: 4
SourcePackage: valgrind
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: memcheck-amd64-linux crashed with SIGILL
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1301850, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :
Download full text (33.2 KiB)

Interesting... I installed the valgrind-dbg package and I no longer get an error report when I attempt to recreate the problem.

Before adding debug this was the output:

$ ./runmysmoketests.sh "valgrind --leak-check=yes -v ./dmcp-debug"
Begining the smoke tests
nc: Address already in use
==4182== Memcheck, a memory error detector
==4182== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==4182== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==4182== Command: ./dmcp-debug
==4182==
--4182-- Valgrind options:
--4182-- --leak-check=yes
--4182-- -v
--4182-- Contents of /proc/version:
--4182-- Linux version 4.13.0-38-generic (buildd@lgw01-amd64-027) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)) #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018
--4182--
--4182-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-avx-avx2-bmi
--4182-- Page sizes: currently 4096, max supported 4096
--4182-- Valgrind library directory: /usr/lib/valgrind
--4182-- Reading syms from /home/thomas/work/src/dmcp/dmcp-debug
--4182-- Reading syms from /lib/x86_64-linux-gnu/ld-2.23.so
--4182-- Considering /lib/x86_64-linux-gnu/ld-2.23.so ..
--4182-- .. CRC mismatch (computed aa979a42 wanted 9019bbb7)
--4182-- Considering /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.23.so ..
--4182-- .. CRC is valid
--4182-- Reading syms from /usr/lib/valgrind/memcheck-amd64-linux
--4182-- Considering /usr/lib/valgrind/memcheck-amd64-linux ..
--4182-- .. CRC mismatch (computed eea41ea9 wanted 2009db78)
--4182-- object doesn't have a symbol table
--4182-- object doesn't have a dynamic symbol table
--4182-- Scheduler: using generic scheduler lock implementation.
--4182-- Reading suppressions file: /usr/lib/valgrind/default.supp
==4182== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-4182-by-thomas-on-???
==4182== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-4182-by-thomas-on-???
==4182== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-4182-by-thomas-on-???
==4182==
==4182== TO CONTROL THIS PROCESS USING vgdb (which you probably
==4182== don't want to do, unless you know exactly what you're doing,
==4182== or are doing some strange experiment):
==4182== /usr/lib/valgrind/../../bin/vgdb --pid=4182 ...command...
==4182==
==4182== TO DEBUG THIS PROCESS USING GDB: start GDB like this
==4182== /path/to/gdb ./dmcp-debug
==4182== and then give GDB the following command
==4182== target remote | /usr/lib/valgrind/../../bin/vgdb --pid=4182
==4182== --pid is optional if only one valgrind process is running
==4182==
--4182-- REDIR: 0x401cfd0 (ld-linux-x86-64.so.2:strlen) redirected to 0x3809e181 (???)
--4182-- Reading syms from /usr/lib/valgrind/vgpreload_core-amd64-linux.so
--4182-- Considering /usr/lib/valgrind/vgpreload_core-amd64-linux.so ..
--4182-- .. CRC mismatch (computed 2567ccf6 wanted 49420590)
--4182-- object doesn't have a symbol table
--4182-- Reading syms from /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so
--4182-- Considering /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so ..
--4182-- .. CRC mismatch (computed 0e27c9a8 wante...

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Closest upstream I came up with was https://bugs.kde.org/show_bug.cgi?id=387940

I cannot confirm if bug #1301850 is a duplicate or not as I cannot view the private bug.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.