apport crashed with SystemError in Unpickler()

[Srik]

Binary package hint: apport

At boot i had this crash.

ProblemType: Crash
Architecture: i386
CrashReports:
 600:1001:1001:2516364:2008-05-24 17:33:13.000000000 +0200:2008-05-24 17:33:06.000000000 +0200:/var/crash/_usr_bin_jockey-gtk.1001.crash
 600:108:118:204338:2008-05-24 17:33:34.000000000 +0200:2008-05-24 17:33:33.000000000 +0200:/var/crash/_usr_lib_gdm_gdmgreeter.108.crash
 600:0:0:469706:2008-05-24 17:35:08.000000000 +0200:2008-05-24 17:35:02.000000000 +0200:/var/crash/_usr_sbin_update-binfmts.0.crash
 600:0:0:7371:2008-05-24 17:35:17.000000000 +0200:2008-05-24 18:19:03.000000000 +0200:/var/crash/_usr_share_apport_apport.0.crash
Date: Sat May 24 17:35:18 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/share/apport/apport
InterpreterPath: /usr/bin/python2.5
Package: apport 0.108.1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/share/apport/apport 6123 11 0
ProcEnviron:

PythonArgs: ['/usr/share/apport/apport', '6123', '11', '0']
SourcePackage: apport
Title: apport crashed with SystemError in Unpickler()
Uname: Linux 2.6.24-16-generic i686
UserGroups:

[Martin Pitt (pitti)]

This crashes while importing the subprocess module, reassigning to python2.5.

[Matthias Klose (doko)]

reassigning to apport; the crash is in the unpickler; maybe a corrupted pickle file?

proposing to close this report if we cannot reproduce it.

[Martin Pitt (pitti)]

Srik, can you reproduce this?

@Matthias: apport doesn't even use pickle. If you look at the stack trace, it doesn't crash during unpickling, but while importing the unpickle module, it fails on the declaration of "dispatch[BININT] = load_binint".

Anyway, this wasn't reported anywhere else, so let's blame this on cosmic rays. Srik, did you get this again? If so, we should reopen this. Thanks!

[Martin Pitt (pitti)]

There are a couple of more duplicates, also for Python 2.6, so this doesn't just look like cosmic rays after all.

Could it be that "unknown opcode" refers to catching a SIGILL? Perhaps Python is built with some instructions that aren't understood by some processors?

[dino99 (9d9)]

Support for this version has ended