dpkg crashed with SIGSEGV in iterpkgnext

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

Bug Description

Binary package hint: dpkg

This crash happened when trying to update via the command line.

Not sure whether it was an aptitude or apt-get command which caused the error.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/dpkg
NonfreeKernelModules: nvidia
Package: dpkg 1.14.24ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: dpkg --configure -a
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: dpkg
Stacktrace:
 #0 0x0805ee43 in ?? ()
 #1 0x0805849a in ?? ()
 #2 0x08055fdd in ?? ()
 #3 0xb7e60775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #4 0x0804ad31 in ?? ()
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.28-9-generic i686
UserGroups:

Revision history for this message
paul_wyatt (wyatt-paul) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:iterpkgnext (i=0x8cf1f70) at ../../lib/database.c:168
packages (argv=0xbf8f8270) at ../../src/packages.c:108
main (argc=3, argv=0xbf8f8270) at ../../src/main.c:638

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in dpkg:
importance: Undecided → Medium
C de-Avillez (hggdh2)
visibility: private → public
summary: - dpkg crashed with SIGSEGV in __libc_start_main()
+ dpkg crashed with SIGSEGV in iterpkgnext
tags: added: apport-request-retrace
Revision history for this message
dino99 (9d9) wrote :

This version has expired long time ago, and 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.