Created attachment 59182 [details]
output of pitivi --gst-debug=*:3,PITIVI:5 2>pitividebug.txt

Created attachment 59183 [details]
output of pitivi --gst-debug=*:3,python:5 2>pitividebug.txt

Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it.
Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

I can't get gdb to work with me, what am I doing wrong?

jeff@khloe:~$ gdb pitivi
This GDB was configured as "i486-linux-gnu"..."/usr/local/bin/pitivi": not in executable format: Format de fichier non reconnu

(gdb) run
Starting program:
No executable file specified.
Use the "file" or "exec-file" command.


I need my hand held for gdb backtracing. So far, I was never able to get a single backtrace correctly no matter what the app maybe I'm just unlucky/goofy :|

Do you at least still get the crash with latest cvs gnonlin and pitivi ?

If you still do, you need to run gdb on python:
gdb python /usr/local/bin/pitivi

The previous command is wrong
it should be: gdb python
and once in gdb: run /usr/local/bin/pitivi

Then follow the instructions as stated here : http://live.gnome.org/GettingTraces#head-b4d479311f06c3c1de7b87af8b9ba83d718fe7f0

(gdb) thread apply all bt

+ Trace 66960

Question: is there a way to tell GDB to just spit the backtrace to an output file? It's really confusing/annoying to copy-paste all this from the terminal in small steps pressing enter each time.

This is a gstreamer issue, marking it as a dupe of #335288

*** This bug has been marked as a duplicate of 335288 ***