Providing information on crashes: Difference between revisions
Created page with "= In general = 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..." |
David tangye (talk | contribs) m →OSX: minor grammar |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
= | = How to report information = | ||
Please create a bug report on: | Please create a bug report on: | ||
| Line 7: | Line 7: | ||
If this is all too complicated you can send an email to bluefish@bluefish.openoffice.nl | 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 = | ||
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 = | = 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) | If Bluefish crashes on OSX there should be a report generated in a separate window. Please copy/paste this information (the backtrace) for thread 0 (on the top of the report) into a 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. | 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. | ||
= Windows = | = Windows = | ||
If you get a dialog "bluefish.exe has stopped working" you can click "view problems" which gives some rudimentary information. Since it is better than nothing, please provide it. | |||
In order to provide more information on Windows you can use the msys debugger, a good tutorial can be found here: | |||
https://github.com/mypaint/mypaint/wiki/Debugging-crashes-on-Windows | |||
Latest revision as of 00:22, 12 July 2022
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 a report generated in a separate window. Please copy/paste this information (the backtrace) for thread 0 (on the top of the report) into a 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.
Windows
If you get a dialog "bluefish.exe has stopped working" you can click "view problems" which gives some rudimentary information. Since it is better than nothing, please provide it.
In order to provide more information on Windows you can use the msys debugger, a good tutorial can be found here: https://github.com/mypaint/mypaint/wiki/Debugging-crashes-on-Windows