|> Mini User manual for GenTle 0.3.5|
I have to write it one more time: REPORTING A BUG IS VERY IMPORTANT. If you know about a bug and you report it, you save a lot of work for other people and you can help to make the software more stable. GenTle contains bugs since I have no time to test it exhaustively. If you report a bug, you save a lot of my time. All right, how can you do it?
If you find a bug, check whether it is reproducible. Try to do the same action as you have done and test if the bug appears again. You can write me about the bug. If the bug leads to crash, continue
If you can reproduce the bug (crash), run GenTle with debugger and reproduce the bug. You need to have GenTle configured with --enable-debug=full option to get meaning-full output from debugger. You can run GenTle with debugger in the following way:
Debugger will start and load all GenTle's debugging symbols. You can enter run command to the debugger and GenTle will start. Reproduce the crash again. Debugger will stop execution of GenTle and will offer you a prompt. Enter info stack command. This command will specify a place of crash with some information about it. Append this listing to your bug report. This significantly decreases my effort when correcting bug.
If you cannot (or don't want) to run GenTle with debugger, you can send me output that GenTle produces to the terminal. As you can see, the output is quite verbose and it can help me to locate the problem (but the debugger report is better for this task ;-)).
Report the bug then. You can do it via GenTle's homepage or via my e-mail (<email@example.com>). I prefer the e-mail way since this way is more quick than the first one. Write a bug description (what actions have you done) and information about a place of bug (from debugger and/or GenTle's terminal output.
Send the report. You are done. Thanks!