dpkg crashed with SIGSEGV in findnamenode()

Bug #560989 reported by Martin Olsson
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
dpkg (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: dpkg

crash.

I don't have repro steps.

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: Sun Apr 11 22:46:19 2010
ExecutablePath: /usr/bin/dpkg
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: /usr/bin/dpkg --status-fd 28 --unpack --auto-deconfigure /var/cache/apt/archives/libwebkit-dev_1.2.0-1_amd64.deb
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x40b49f: cmpb $0x2f,(%rdi)
 PC (0x0040b49f) ok
 source "$0x2f" ok
 destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: dpkg
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: dpkg crashed with SIGSEGV
UserGroups:

Revision history for this message
Martin Olsson (mnemo) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 findnamenode (
 pkg_files_add_file (pkg=0x12315d0,
 ensure_packagefiles_available (pkg=0x12315d0)
 ensure_allinstfiles_available ()
 process_archive (filename=<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
summary: - dpkg crashed with SIGSEGV
+ dpkg crashed with SIGSEGV in findnamenode()
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.