Ubuntu
dpkg package

update-alternatives crashed with SIGSEGV in __libc_start_main()

Bug #615158 reported by Roy on 2010-08-08

This bug report is a duplicate of: Bug #615100: update-alternatives crashed with SIGSEGV in __libc_start_main(). Edit Remove

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	dpkg (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

I was doing a normal update in Lucid on a computer that had not been updated in the last couple of weeks. When the update finished I found I had unknowingly upgraded to Maverick. Fortunately this happened on a computer that just runs BOINC and not on one of my main computers. At any rate when the update finished the crash symbol was displayed and this is the result.

1 About Ubuntu shows the system as being 10.04 Lucid. Software sources is showing Maverick. Sysinfo crashes.
2 Since I really don't know what happened I have no idea what package is creating the problem
3 I expected an update of Lucid.
4 I wound up with an upgrade to Maverick.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: dpkg 1.15.8.2ubuntu3
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
Date: Sun Aug 8 16:43:57 2010
ExecutablePath: /usr/bin/update-alternatives
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100630.2)
ProcCmdline: update-alternatives --remove-all ps2pdf
ProcEnviron:
PATH=(custom, no user)
LANG=en_CA.UTF8
SegvAnalysis:
Segfault happened at: 0xa101aa: cmp (%edx),%al
PC (0x00a101aa) ok
source "(%edx)" (0x00000019) not located in a known VMA region (needed readable region)!
destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: dpkg
StacktraceTop:
?? () from /lib/libc.so.6
?? ()
?? ()
__libc_start_main () from /lib/libc.so.6
?? ()
Title: update-alternatives crashed with SIGSEGV in __libc_start_main()
UserGroups:

Tags:

Revision history for this message

Roy (rdstrac) wrote on 2010-08-08:

Dependencies.txt Edit (548 bytes, text/plain; charset="utf-8")
Disassembly.txt Edit (403 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (1.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (731 bytes, text/plain; charset="utf-8")
Registers.txt Edit (469 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (334 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (360 bytes, text/plain; charset="utf-8")

visibility:

private → public

Brian Murray (brian-murray) on 2010-08-30

affects:

ubuntu → dpkg (Ubuntu)

Revision history for this message

Rolf Leggewie (r0lf) wrote on 2010-09-07:

confirming this ticket based on bug 617220

Changed in dpkg (Ubuntu):
importance:	Undecided → Medium
status:	New → Confirmed

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-09:

StacktraceTop:
*__GI_strcoll (s1=0xbfaabe07 "remove-all",
main (argc=3, argv=0xbfaaa2c4)

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-09: Stacktrace.txt

Stacktrace.txt Edit (602 bytes, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2010-09-09: ThreadStacktrace.txt

ThreadStacktrace.txt Edit (629 bytes, text/plain)

tags:

removed: need-i386-retrace

Revision history for this message

roscio1975 (stefano-manocchio-gmail) wrote on 2010-09-18:

Occurs also to me on maverick x86

Revision history for this message

Brian Murray (brian-murray) wrote on 2010-11-23:

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.