update-alternatives crashed with SIGSEGV in __strcmp_sse4_2()

Bug #615195 reported by Andrew Bennetts
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: dpkg

I don't know what triggered this. Apport just informed me there had been a crash with no context.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: dpkg 1.15.8.2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-14.19-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
Date: Mon Aug 9 12:37:51 2010
ExecutablePath: /usr/bin/update-alternatives
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: update-alternatives --remove-all ps2pdf
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_AU.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x3ea09f <__strcmp_sse4_2+47>: cmp (%eax),%ecx
 PC (0x003ea09f) ok
 source "(%eax)" (0x00000020) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: dpkg
StacktraceTop:
 __strcmp_sse4_2 () at ../sysdeps/i386/i686/multiarch/strcmp-sse4.S:76
 ?? ()
 ?? ()
 __libc_start_main (main=0x804b510, argc=3,
 ?? ()
Title: update-alternatives crashed with SIGSEGV in __strcmp_sse4_2()
UserGroups:

Revision history for this message
Andrew Bennetts (spiv) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __strcmp_sse4_2 ()
 ?? ()
 main (argc=3, argv=0xbfe42b54)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in dpkg (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 615100, so it 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.

visibility: private → public
Changed in dpkg (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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