[Bug 1765001] Re: memcheck-amd64-linux crashed with SIGILL during valgrind --leak-check of my binary

Apport retracing service 1765001 at bugs.launchpad.net
Wed Apr 18 10:39:59 UTC 2018


*** This bug is a duplicate of bug 1301850 ***
    https://bugs.launchpad.net/bugs/1301850

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.

** Attachment removed: "CoreDump.gz"
   https://bugs.launchpad.net/bugs/1765001/+attachment/5120728/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   https://bugs.launchpad.net/bugs/1765001/+attachment/5120730/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/1765001/+attachment/5120734/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/1765001/+attachment/5120735/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   https://bugs.launchpad.net/bugs/1765001/+attachment/5120736/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   https://bugs.launchpad.net/bugs/1765001/+attachment/5120737/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   https://bugs.launchpad.net/bugs/1765001/+attachment/5120738/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1301850

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to valgrind in Ubuntu.
https://bugs.launchpad.net/bugs/1765001

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

Status in valgrind package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1765001/+subscriptions



More information about the foundations-bugs mailing list