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

Bug #1292763 reported by Brian G. Marete
42
This bug affects 4 people
Affects Status Importance Assigned to Milestone
eglibc (Debian)
New
Unknown
eglibc (Ubuntu)
Fix Released
Medium
Rolf Leggewie

Bug Description

This happened when I was running `update-manager', when it was configuring packages at the end.

In the kernel log, I find:

[146936.255567] traps: ld-linux-x32.so[26237] general protection ip:f7715ced sp:ff8372a8 error:0 in ld-2.19.so[f76ff000+20000]
[146936.617914] traps: ld-linux-x32.so[26247] general protection ip:f778aced sp:ffd435c8 error:0 in ld-2.19.so[f7774000+20000]
[146936.794923] traps: ld-linux-x32.so[26257] general protection ip:f776eced sp:ffd19978 error:0 in ld-2.19.so[f7758000+20000]

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libc6-x32 2.19-0ubuntu2
Uname: Linux 3.13.6 x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Mar 14 13:51:30 2014
Dependencies:
 gcc-4.9-base 4.9-20140303-0ubuntu3
 libc6 2.19-0ubuntu2
 libgcc1 1:4.9-20140303-0ubuntu3
 multiarch-support 2.19-0ubuntu2
Disassembly: value is not available
ExecutablePath: /libx32/ld-2.19.so
InstallationDate: Installed on 2011-02-28 (1110 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: /libx32/ld-linux-x32.so.2
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcMaps:
 f772c000-f772d000 r-xp 00000000 00:00 0 [vdso]
 f772d000-f774d000 r-xp 00000000 08:01 22151174 /libx32/ld-2.19.so
 f794c000-f794e000 rw-p 0001f000 08:01 22151174 /libx32/ld-2.19.so
 ffc0d000-ffc2e000 rw-p 00000000 00:00 0 [stack]
SegvAnalysis: Failure: invalid literal for int() with base 16: '<unavailable>'
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 13235):
 #0 <unavailable> in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further
Title: ld-2.19.so crashed with SIGSEGV in <unavailable> in ??()
UpgradeStatus: Upgraded to trusty on 2014-03-13 (2 days ago)
UserGroups: pkcs11

Revision history for this message
Brian G. Marete (bgmarete) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

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 13235):
 #0 <unavailable> in ?? ()
 PC unavailable, cannot determine locals.
 Backtrace stopped: not enough registers or memory available to unwind further

Changed in eglibc (Ubuntu):
importance: Undecided → Medium
summary: - ld-2.19.so crashed with SIGSEGV in <unavailable> in ??()
+ ld-2.19.so crashed with SIGSEGV in <unavailable> in <unavailable> in
+ ??()
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Rolf Leggewie (r0lf) wrote :

This seems to occur only in libc-x32. Reports so far are only for 14.04/trusty. Can anybody reproduce this on a later release?

Changed in eglibc (Ubuntu):
assignee: nobody → Rolf Leggewie (r0lf)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in eglibc (Ubuntu):
status: New → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I intend to close this ticket as fix released soon (based on bug 1302903 comment 1). Please speak up if you still experience this.

Changed in eglibc (Debian):
status: Unknown → New
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Closing

Changed in eglibc (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.