pitivi crashed with SIGSEGV in PyEval_EvalCodeEx()

Bug #649096 reported by miniX on 2010-09-27
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pitivi (Ubuntu)

Bug Description

Binary package hint: pitivi

It looks more like bug no 635622. But i am using 64 bit version

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pitivi 0.13.5-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Mon Sep 27 20:46:28 2010
ExecutablePath: /usr/bin/pitivi
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: python /usr/bin/pitivi
 Segfault happened at: 0x4a63a9 <PyEval_EvalCodeEx+233>: addq $0x1,(%rax)
 PC (0x004a63a9) ok
 source "$0x1" ok
 destination "(%rax)" (0x00000000) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: pitivi
 #0 0x00000000004a63a9 in PyEval_EvalCodeEx ()
 No symbol table info available.
 Cannot access memory at address 0x7fff0f168c88
StacktraceTop: PyEval_EvalCodeEx ()
Title: pitivi crashed with SIGSEGV in PyEval_EvalCodeEx()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

miniX (lijoyx) wrote :

StacktraceTop: PyEval_EvalCodeEx (co=0x304a0a8, globals=<value optimized out>,

Changed in pitivi (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Jeff Fortin Tam (kiddo) on 2010-09-29
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