python2.6 crashed with SIGSEGV

Bug #599042 reported by YannUbuntu on 2010-06-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python2.6 (Ubuntu)

Bug Description

Binary package hint: python2.6

Crash of Muji

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: python2.6-minimal 2.6.5-1ubuntu6
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
CheckboxSubmission: 7bf4676ac92338d1d362954586c33b04
CheckboxSystem: bd9978d0ff03d4f55482fc24a6cdac35
CrashCounter: 1
Date: Sun Jun 27 23:38:50 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/python2.6
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100328)
ProcCmdline: python new-call-demo/
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: python2.6
 #0 0x00000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xb38fd02c
StacktraceTop: ?? ()
Title: python2.6 crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare src

YannUbuntu (yannubuntu) wrote :
visibility: private → public
Brian Curtis (bcurtiswx) wrote :

Thanks for your bug report. Right now there are tasks that apport needs to perform on this bug before we can go any further. Please wait for this, and we will start triaging your bug when this is complete. Thanks for your patience. This bug needs to stay private.

visibility: public → private
YannUbuntu (yannubuntu) wrote :

ok, just tell me if you need me to do something.

 #0 0x00000000 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0xb38fd07c
StacktraceTop: ?? ()

Changed in python2.6 (Ubuntu):
status: New → Invalid

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libc-bin: installed version 2.11.1-0ubuntu7.1, latest version: 2.11.1-0ubuntu7.2
libc6: installed version 2.11.1-0ubuntu7.1, latest version: 2.11.1-0ubuntu7.2
dpkg: installed version, latest version:

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-i386-retrace
YannUbuntu (yannubuntu) wrote :

My Lucid system is up-to-date ! (And my software sources are from the Main server, I think it is the first to be updated, isn't it?)

Synaptic indicates that I have the latest versions for the 3 packages you mention.

visibility: private → public
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers