SegvAnalysis: Failure: invalid literal for int() with base 16: '='
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
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
ThreadStack
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
ProcVersionSign
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)
PackageArchitec
SourcePackage: apport
UpgradeStatus: Upgraded to vivid on 2015-04-23 (14 days ago)
You can see the Disassembly: field contains
$2 = -99Python Exception <class 'TypeError'> iter() returned non-iterator of type '_iterator':
which is missing a newline. This breaks apport's output splitting logic.
The TypeError shows up because of bug 1449389. I think it gets printed into the standard error, which is then smushed together with the standard output in a somewhat random way.