Bug #437124 “dpkg crashed with SIGSEGV in __libc_start_main()” : Bugs : dpkg package : Ubuntu

dpkg crashed with SIGSEGV in __libc_start_main()

Bug #437124 reported by Moti Ochayun
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: dpkg

i did upgrade

ProblemType: Crash
Architecture: i386
Date: Sat Sep 26 13:35:01 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/dpkg
Package: dpkg 1.15.4ubuntu2
ProcCmdline: /usr/bin/dpkg --status-fd 34 --unpack --auto-deconfigure /var/cache/apt/archives/libtidy-0.99-0_20081224cvs-1_i386.deb /var/cache/apt/archives/python-chardet_1.0.1-1.1_all.deb /var/cache/apt/archives/python-evolution_2.28.0-0ubuntu1_i386.deb /var/cache/apt/archives/python-feedparser_4.1-14_all.deb /var/cache/apt/archives/python-gtkmozembed_2.25.3-2ubuntu2.0xul191_i386.deb /var/cache/apt/archives/python-rsvg_2.28.0-0ubuntu1_i386.deb /var/cache/apt/archives/python-utidylib_0.2-3.2ubuntu1_all.deb /var/cache/apt/archives/python-wnck_2.28.0-0ubuntu1_i386.deb /var/cache/apt/archives/screenlets_0.1.2-7_all.deb
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
 Segfault happened at: 0x8053388: movl $0x0,0x14(%eax)
 PC (0x08053388) ok
 source "$0x0" ok
 destination "0x14(%eax)" (0x72737543) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: dpkg
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
Title: dpkg crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.31-11-generic i686
UserGroups:

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #359127, so 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
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Loading subscribers...

Remote bug watches

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