Comment 3 for bug 247018

Laszlo Pandy (laszlok) wrote :

I am assuming since you are using Hardy that the Python version you have is 2.5. You can check this with:
  python --version

You need to install the Ubuntu package python2.5-dbg. If you are using python 2.4, then install python2.4-dbg.

Here are the other debugging packages required to get a proper stacetrace of jokosher:
libgstreamer0.10-0-dbg
gstreamer0.10-plugins-base-dbg
gstreamer0.10-plugins-good-dbg
gstreamer0.10-plugins-ugly-dbg
gdb

All of those are debugging symbols for Gstreamer, except the last one which is the GNU Debugger.

Now you can run Jokosher in the debugger to try and get a stack trace. Run the following command:
  gdb --args python /usr/bin/jokosher

When you see the (gdb) prompt, enter "run":
(gdb) run
Starting program: /usr/bin/python /usr/bin/jokosher
[Thread debugging using libthread_db enabled]
[New Thread 0xb7d7e6b0 (LWP 17916)]

Program received signal SIGINT, Interrupt.
[Switching to Thread 0xb7d7e6b0 (LWP 17916)]
0xb7f2c410 in __kernel_vsyscall ()
(gdb)

You should see the same thing, except the signal name will be SIGSEGV instead meaning Segmentation Fault.
At this point you are given the (gdb) prompt again, and we will enter the command backtrace:
(gdb) backtrace
#0 0xb7f2c410 in __kernel_vsyscall ()
#1 0xb7e4cbcb in poll () from /lib/tls/i686/cmov/libc.so.6
#2 0xb7bb91c6 in ?? () from /usr/lib/libglib-2.0.so.0
#3 0xb7bb9577 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#4 0xb772a264 in IA__gtk_main ()

Your backtrace will look something like that. If it is too long to fit in the screen you may need to press enter a couple of times to see it all. Copy and paste the section from #0 to the very last line in the terminal into this bug report and I will analyse it.