pitivi crashed with SIGSEGV in PyEval_EvalCodeEx()

Bug #648208 reported by bill on 2010-09-26
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pitivi (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: pitivi

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pitivi 0.13.5-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 26 11:58:21 2010
ExecutablePath: /usr/bin/pitivi
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100831.2)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: python /usr/bin/pitivi
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 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
StacktraceTop:
 PyEval_EvalCodeEx ()
 ?? ()
 PyObject_Call ()
 ?? ()
 PyObject_Call ()
Title: pitivi crashed with SIGSEGV in PyEval_EvalCodeEx()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video

bill (bill-lm) wrote :

StacktraceTop:
 PyEval_EvalCodeEx (co=0x26cc288, globals=<value optimized out>,
 function_call (func=0x273f410, arg=0x3bbb050,
 PyObject_Call (func=0x273f410, arg=0x8265c0,
 instancemethod_call (func=0x273f410, arg=0x3bbb050,
 PyObject_Call (func=0x2d28c80, arg=0x8265c0,

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