Dyne Backtraching Howto
Suppose that you have installed the latest version of freej or muse or others dyne software, and inexplicably going crash. For this you are unhappy, and mocks jokingly the programmers :P, but in reality you want kill these! Then...backtrace may help programmers for the bugs correction and for live in happiness with the free software!!! If you want an even better software you have to help the developper with your small contribution. In this page we explain how to make an helpfull backtrace from a reproducible program crash.
First of all you have to install the debugger program:
- On a Debian/Ubuntu:
- On a Gentoo:
pacman -S gdb
For the other distributions you have to install gdb
When install a software from binary the debug options are disabled by default. Then you have to re-install the package from source making sure that is enabled the option --enable-debug or passing to the compiler the option -ggdb. After this we can proceed to obtain a program backtrace. Point gdb to the path of the program to run and give it the arguments it will need; then run it:
gdb /path/to/program/<program> [...] (gdb) run <program_options> [...] (gdb) set logging file <namefile_backtrace> (gdb) set logging on Copying output to <namefile_backtrace>. (gdb) bt full ... ... (gdb) set logging off Done logging to <namefile_backtrace>. (gdb) quit
Replace the <program_options> with the cmd options that the program need! If the program no need other options you have to do only "run".
Replace the <namefile_backtrace> with an output file name for store the backtrace log. Note that the backtrace log is stored on path where you launches the gdb program.
Submit the backtrace log to http://bugs.dyne.org or join on irc.hinezumi.org, SSL(accept wrong certificates) , port 9999 to #dyne channel and paste it on the channel with nopaste or dpaste link and awaits a response from developers.