Ubuntu
python2.5 package

apport-checkreports crashed with SIGSEGV while booting the Gutsy LiveCD

Bug #172935 reported by Rob Oxspring on 2007-11-29

6

Affects		Status	Importance	Assigned to	Milestone
	python2.5 (Ubuntu)	Invalid	Medium	Unassigned

Bug Description

Binary package hint: apport

All I did was boot the Gutsy i386 Live CD

ProblemType: Crash
Architecture: i386
CrashReports:
600:999:999:1196313:2007-11-29 23:05:38.684869000 +0000:2007-11-29 23:05:39.684869000 +0000:/var/crash/_usr_bin_gnome-power-manager.999.crash
0:999:999:286643:2007-11-29 23:06:00.696566316 +0000:2007-11-29 23:05:52.692110000 +0000:/var/crash/_usr_share_apport_apport-checkreports.999.crash
Date: Thu Nov 29 23:05:48 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/share/apport/apport-checkreports
InterpreterPath: /usr/bin/python2.5
NonfreeKernelModules: cdrom
Package: apport 0.98
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport-checkreports
ProcCwd: /home/ubuntu
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: apport
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
Title: apport-checkreports crashed with SIGSEGV
Uname: Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Tags:

Revision history for this message

Rob Oxspring (roxspring) wrote on 2007-11-29:

#1

ApportLog.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (480 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (5.0 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (660 bytes, text/plain; charset="utf-8")
Registers.txt Edit (458 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (252 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (279 bytes, text/plain; charset="utf-8")

Siegfried Gevatter (rainct) on 2007-12-08

Changed in apport:
importance:	Undecided → Medium

Revision history for this message

Apport retracing service (apport) wrote on 2008-02-05: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (26.2 KiB, text/plain)

StacktraceTop:visit_decref (op=0xb7dffacc, data=0x0) at ../Modules/gcmodule.c:270
frame_traverse (f=0x81be814, visit=0x80f2a50 <visit_decref>, arg=0x0)
collect (generation=1) at ../Modules/gcmodule.c:295
_PyObject_GC_New (tp=0x815e8a0) at ../Modules/gcmodule.c:897
PyFunction_New (code=0xb7a07188, globals=0xb79e59bc) at ../Objects/funcobject.c:12

Revision history for this message

Apport retracing service (apport) wrote on 2008-02-05: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (26.3 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2008-02-05: Stack trace with source code

#4

StacktraceSource.txt Edit (6.7 KiB, text/plain)

Revision history for this message

Martin Pitt (pitti) wrote on 2008-02-05:

#5

Crash in python interpreter, has verbose stack trace

Revision history for this message

Simon Déziel (sdeziel) wrote on 2008-04-09:

#6

I think that I just identified my problem : bad RAM. Sorry for wasting your time.

Revision history for this message

Matthias Klose (doko) wrote on 2008-09-12:

#7

> I think that I just identified my problem : bad RAM. Sorry for wasting your time.

closing.

Changed in python2.5:
status:	New → Invalid

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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