pitivi crashed with SIGSEGV in PyEval_EvalCodeEx()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pitivi (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: pitivi
i was trying to use pitivi and it crashed. I dragged on video clip into the time line it was ok till then . but when i tried to drag another clip it crashed and this bug report thing poped up.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: pitivi 0.13.4-3ubuntu1
Uname: Linux 2.6.35-997-generic i686
Architecture: i386
CrashCounter: 1
Date: Wed Aug 4 22:38:02 2010
ExecutablePath: /usr/bin/pitivi
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: python /usr/bin/pitivi
ProcEnviron:
LANG=en_US.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x80e1caa <PyEval_
PC (0x080e1caa) ok
source "$0x1" ok
destination "(%edx)" (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 cdrom dialout lpadmin plugdev sambashare
Changed in pitivi (Ubuntu): | |
status: | New → Triaged |
status: | Triaged → New |
Changed in pitivi (Ubuntu): | |
status: | New → Confirmed |
Without precise repro instructions, this is not helpful in knowing what happened. It needs to be consistently reproducible, and ideally with debug logs. You could create debug logs by running pitivi like this, for example:
PITIVI_DEBUG=*:5 GST_DEBUG=2 /usr/bin/pitivi > debug.log 2>&1