dpkg crashed with SIGSEGV in parsedb()

Bug #559397 reported by peanut
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: dpkg

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: dpkg 1.15.5.6ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic x86_64
Architecture: amd64
Date: Fri Apr 9 18:17:26 2010
ExecutablePath: /usr/bin/dpkg
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
ProcCmdline: dpkg --get-selections
ProcEnviron:
 SHELL=/bin/zsh
 PATH=(custom, user)
 LANG=nl_BE.utf8
 LANGUAGE=en
SegvAnalysis:
 Segfault happened at: 0x41c585: cmpb $0x0,(%rdx)
 PC (0x0041c585) ok
 source "$0x0" ok
 destination "(%rdx)" (0x40000000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: dpkg
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
Title: dpkg crashed with SIGSEGV in __libc_start_main()
UserGroups:

Revision history for this message
peanut (rik-vanmechelen) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 parsedb (filename=<value optimized out>, flags=<value optimized out>,
 modstatdb_init (adir=0x44e8a5 "/var/lib/dpkg",
 getselections (argv=0x7fffb087a388)
 main (argc=<value optimized out>,

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-amd64-retrace
visibility: private → public
summary: - dpkg crashed with SIGSEGV in __libc_start_main()
+ dpkg crashed with SIGSEGV in parsedb()
tags: added: apport-request-retrace
Revision history for this message
dino99 (9d9) wrote :

That version is no more supported

Changed in dpkg (Ubuntu):
status: New → Invalid
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.