memcheck-amd64-linux crashed with SIGILL during valgrind --leak-check of my binary
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~
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
ProcVersionSign
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/
InstallationDate: Installed on 2017-11-16 (152 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcCmdline: /usr/bin/
Signal: 4
SourcePackage: valgrind
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: memcheck-
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip docker lpadmin plugdev sambashare sudo wireshark
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.