Here are the detailed steps for sending a useful backtrace to the Bluefish Developer Team.
Procedure X.1. Running bluefish under gdb
Get the latest CVS release (see Section 4, “Latest Developmental Version” for info)
From bluefish-gtk2, the top directory of the bluefish source, run: autoconf
You may have to set some environment variables before running autoconf, as well as providing autoconf with some flags. Also, some patches may need to be applied, depending on your system.
Then, run ./configure --with-debugging-output
Again, you may have to add some flags, depending on your system.
Once you succeed in configuring bluefish, run: make clean in order to remove all unnecessary files.
Then, run make to compile bluefish.
Do not run make install since it strips the debugging symbols from the executable.
Execute bluefish under gdb with: gdb src/bluefish. This way, you will get access to a non stripped version of bluefish, which is not the case if you run gdb bluefish or gdb /usr/local/bin/bluefish, since those binaries do not have any debugging symbols anymore.
Once gdb has started, type r to start the debugging session.
Try to reproduce the crash in bluefish.
Copy and paste the last 50 lines of debugging output to a text file.
Type bt in gdb to get the backtrace, and copy it to the text file too. If the backtrace is huge, copy only the first 50 lines.
Save the text file and gzip it by running gzip textfile in a terminal.
Quit gdb with q
Fill in the bug report (see Section 2, “Filling a bug report” for instructions).