desktop-packages team mailing list archive

[Marius Gedminas <marius@xxxxxxxxx>]

Public bug reported:

Apport sometimes gets confused when analyzing a core dump:

    SegvAnalysis: Failure: invalid literal for int() with base 16: '='

I'm attaching the crash file (sans base64-encoded core dump) that
contains this and some other wonderful examples, like

    Registers: $6 = 0x0                                                                                                                         
    ThreadStacktrace: $9 = 0x4 <error: Cannot access memory at address 0x4>                                                                     
    Stacktrace: No symbol "__nih_abort_msg" in current context.

and the Disassembly: field containing the actual stack trace, after the
disassembly itself.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apport 2.17.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri May  8 10:17:40 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-07-25 (1016 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to vivid on 2015-04-23 (14 days ago)

** Affects: apport (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug gnome3-ppa third-party-packages vivid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1453011

Title:
  SegvAnalysis: Failure: invalid literal for int() with base 16: '='

Status in apport package in Ubuntu:
  New

Bug description:
  Apport sometimes gets confused when analyzing a core dump:

      SegvAnalysis: Failure: invalid literal for int() with base 16: '='

  I'm attaching the crash file (sans base64-encoded core dump) that
  contains this and some other wonderful examples, like

      Registers: $6 = 0x0                                                                                                                         
      ThreadStacktrace: $9 = 0x4 <error: Cannot access memory at address 0x4>                                                                     
      Stacktrace: No symbol "__nih_abort_msg" in current context.

  and the Disassembly: field containing the actual stack trace, after
  the disassembly itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
  Uname: Linux 3.19.0-16-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri May  8 10:17:40 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-07-25 (1016 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (14 days ago)

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