espeak-gui crashed with SIGSEGV in Py_BuildValue()

Bug #906697 reported by Juan Lee
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
espeak-gui (Ubuntu)
New
Undecided
Unassigned

Bug Description

1) Realese - 12.4 Precise
2) Version of package - eSpeak Speach sythesizer version: 1.45.04-2ubuntu1
3) What you expected to happen - Tried to execute program
4) What happened instead - Program consistently crashes before loading

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: espeak-gui 0.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-5.11-generic 3.2.0-rc5
Uname: Linux 3.2.0-5-generic x86_64
ApportVersion: 1.90-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Dec 19 21:47:29 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/share/espeak-gui/espeak-gui
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/espeak-gui
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x4d8eab: repnz scas %es:(%rdi),%al
 PC (0x004d8eab) ok
 source "%es:(%rdi)" (0x7f0300000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: espeak-gui
StacktraceTop:
 ?? ()
 ?? ()
 Py_BuildValue ()
 ?? () from /usr/lib/pymodules/python2.7/espeak/core.so
 PyEval_EvalFrameEx ()
Title: espeak-gui crashed with SIGSEGV in Py_BuildValue()
UpgradeStatus: Upgraded to precise on 2011-12-05 (14 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Juan Lee (happymisanthrope) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #860307, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-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.