pep/blog.bouah.net
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Remove 'Existing tools' section, move content down to Reproducibility

Browse source 
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
Maxime “pep” Buquet 2019-04-06 13:58:14 +01:00
parent 69351c59b6
commit 36e96fe8d5
Signed by: pep
GPG key ID: DEDA74AEECA9D0F2
1 changed files with 9 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
content/posts/how-to-write-a-good-bug-report.md
View file

@ -100,19 +100,6 @@ it makes it easier to isolate and track. People on the other side will be
more capable at helping you with precise indications. It happens that you do
not know, and in this case they might guide you and/or split the task for you.
### Existing tools
Some applications already include automatic bug/crash reporting. For example
in [Firefox][crash-report] if you type "about:crashes" in the URL bar, you
will get a list of all crash reports that have been generated for you and sent
to Mozilla servers if you so chose at the time. These reports include data
useful for developers to find the cause of the crash.
Often it is still good to have a bug report tracking a particular issue. In
this case you can link one or multiple related crash reports in it.
[crash-report]: https://support.mozilla.org/en-US/kb/mozillacrashreporter
### Reproducibility
This part is about writing down the steps that lead you to the issue. These
@ -137,6 +124,13 @@ You can usually get all this information in the help menus of applications.
![][gnome-version].
Some applications already include automatic bug/crash reporting. For example
in [Firefox][crash-report] if you type "about:crashes" in the URL bar, you
will get a list of all crash reports that have been generated for you and sent
to Mozilla servers if you so chose at the time. These reports include data
useful for developers to find the cause of the crash.
As sysadmin, what I will be looking after is patterns, to try and identify
what part of the system and software is responsible, where the issue lies and
if there is code to fix for it, or if it is a configuration or user mistake.
@ -145,6 +139,8 @@ It often feels to me like playing detectives. The more patterns I observe, the
more suspects I can cross off my list. It is rewarding to finally solve a
complex case, but "boring" ones also help with mental health.
[crash-report]: https://support.mozilla.org/en-US/kb/mozillacrashreporter
### What happens?
Did anything happen at all?