Archlinux.fr [Forums]

ekiga.org a écrit : How to get a stack backtrace from a crash or freeze

This stack backtrace is needed only when ekiga crashes or when ekiga freezes.
Pre-requisites

Emblem-important.png First, you need to install the GNU Project Debugger gdb.

If you use packages from your gnu/linux distribution, then you need to install debug packages for ptlib, opal and ekiga, whose name end generally in -dbg or -dbgsym, such as libpt-...-dbg (e.g. for ubuntu read DebuggingProgramCrash). These debug packages are additional packages that do not affect your existing program, but provide extra information (debugging symbols) needed by developers. This makes it a lot easier to find the exact place in the program code where that problem occurs, and to fix it.

If you have compiled ptlib, opal and ekiga yourself, you have nothing to do (by default, compilation is with debug symbols).

Getting the stack backtrace

In a terminal, type:

Code : Tout sélectionner

$ gdb ekiga 2>&1 | tee gdb-ekiga.txt
(gdb) run

Note: it's better to enable debug output in the same time. You can start ekiga in a new terminal like this:

Code : Tout sélectionner

$ gdb --args ekiga -d 4 2>&1 | tee gdb-ekiga.txt
(gdb) run

Now Ekiga should run normally. Perform the action you did to make it crash, then go back to the terminal window and you should see something like SIGSEGV at... If Ekiga freeze, go back to the terminal window and hit CTRL-C.

At this stage type:

Code : Tout sélectionner

(gdb) thread apply all bt
(gdb) quit

The file gdb-ekiga.txt has the backtrace you need to send us (see below for how to send it).