ld-2.17.so crashed with SIGSEGV in <unavailable> in <unavailable> in ??()

[Karl Hegbloom]

IIRC, this apport crash dialog appeared after the intial reboot into Raring on upgrade from Quantal. I do not know whether the core dump was from before or after the reboot.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: libc6-x32 2.17-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-25.39~ppa1-generic-tuxonice 3.5.7.4
Uname: Linux 3.5.0-25-generic-tuxonice x86_64
ApportVersion: 2.9.1-0ubuntu1
Architecture: amd64
Date: Sun Mar 10 22:56:45 2013
Disassembly: value is not available
ExecutablePath: /libx32/ld-2.17.so
InstallationDate: Installed on 2012-10-27 (135 days ago)
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2)
MarkForUpload: True
ProcCmdline: /libx32/ld-linux-x32.so.2 --verify /etc/initramfs-tools/conf.d/mdadm
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=<set>
ProcMaps:
 f76de000-f76df000 r-xp 00000000 00:00 0 [vdso]
 f76df000-f7700000 r-xp 00000000 fc:02 3014667 /libx32/ld-2.17.so
 f78ff000-f7901000 rw-p 00020000 fc:02 3014667 /libx32/ld-2.17.so
 ffb15000-ffb36000 rw-p 00000000 00:00 0 [stack]
SegvAnalysis: Failure: invalid literal for int() with base 16: '*value'
Signal: 11
SourcePackage: eglibc
Stacktrace:
 #0 <unavailable> in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further
StacktraceTop: <unavailable> in ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 16292):
 #0 <unavailable> in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further
Title: ld-2.17.so crashed with SIGSEGV in <unavailable> in ??()
UpgradeStatus: Upgraded to raring on 2013-03-11 (0 days ago)
UserGroups:

[Karl Hegbloom (karl.hegbloom)]

Note: I had not upgraded to the newest kernel prior to the reboot, and was still running the 3.5 tuxonice one at that point. I've never seen this crash before, with Quantal or earlier, so I don't believe it's kernel related... but have no firm opinion since I've not even looked at the stack trace or anything myself.

[Apport retracing service (apport)]

Stacktrace:
 #0 <unavailable> in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further
StacktraceSource: #0 <unavailable> in ?? ()
StacktraceTop: <unavailable> in ?? ()
ThreadStacktrace:
 .
 Thread 1 (LWP 16292):
 #0 <unavailable> in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further