python2.7 crashed with SIGSEGV in void WTF::dtoa<true, false, false, true>()

Bug #949397 reported by joshg
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python2.7 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

USC crashes after clicking on "buy.." button.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: python2.7-minimal 2.7.2-13ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
Date: Wed Mar 7 22:08:30 2012
ExecutablePath: /usr/bin/python2.7
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110904)
ProcCmdline: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x1ded0e3 <_ZN3WTF4dtoaILb1ELb0ELb0ELb1EEEvPcdiRbRiRj+963>: mov %dl,(%eax)
 PC (0x01ded0e3) ok
 source "%dl" ok
 destination "(%eax)" (0xbffd0000) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: python2.7
StacktraceTop:
 void WTF::dtoa<true, false, false, true>(char*, double, int, bool&, int&, unsigned int&) () from /usr/lib/libjavascriptcoregtk-3.0.so.0
 WTF::dtoa(char*, double, bool&, int&, unsigned int&) () from /usr/lib/libjavascriptcoregtk-3.0.so.0
 ?? () from /usr/lib/libwebkitgtk-3.0.so.0
 ?? ()
 ?? ()
Title: python2.7 crashed with SIGSEGV in void WTF::dtoa<true, false, false, true>()
UpgradeStatus: Upgraded to precise on 2012-03-03 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare scanner

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

Stacktrace:
 #0 0x01ded0e3 in ?? ()
 No symbol table info available.
 Backtrace stopped: Not enough registers or memory available to unwind further
StacktraceTop: ?? ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in python2.7 (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

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

package python-gobject-cairo does not exist, ignoring

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
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.