Providing information on crashes

How to report information

Please create a bug report on: https://sourceforge.net/p/bluefish/tickets/

Or subscribe to the bluefish community mailinglist.

If this is all too complicated you can send an email to bluefish@bluefish.openoffice.nl

What to send

In general: It is always a good idea to tell us your version of Bluefish and your version of GTK/Glib installed on your system, both can be found in the About menu. Please copy/paste the information in Help->Build info

Also don't forget to mention the platform (Linux, OSX, Windows, FreeBSD, etc.) and it's version (and for Linux the distribution). If you have the possibility to test it on multiple computers with different platforms or versions this will really help to track down the problem. If you can reproduce a crash on some specific file, please send us the file too. The smaller the file, the easier for us to debug the issue.

Linux

Linux has a wealth of tools to track down problems in software. Please have a look at https://bfwiki.tellefsen.net/index.php/Debugging_Bluefish for a detailed description on what is possible.

OSX

If Bluefish crashes on OSX there should be report generated in separate window. Please copy/paste this information (the backtrace) for thread 0 (on the top of the report) to text file and send it to the bluefish developers. Preferably create a bug report on https://sourceforge.net/p/bluefish/tickets/ and attach it as a text file.

On OSX you can run Bluefish via terminal, that provides some debug output that might help to identify issue. Open terminal and type: /Applications/Bluefish.app/Contents/MacOS/bluefish (assuming that Bluefish is installed in the Applications folder). Please copy/paste the terminal output to a text file and attach it as well.