Changes between Version 13 and Version 14 of ReportingBugs


Ignore:
Timestamp:
Dec 16, 2017, 6:18:45 PM (21 months ago)
Author:
humdinger
Comment:

Update. gdb -> Debugger

Legend:

Unmodified
Added
Removed
Modified
  • ReportingBugs

    v13 v14  
    2020  1. Describe what steps you need to perform in order to expose the bug. This will help developers reproduce the bug.
    2121  1. Attach as much information as you have. If it is a GUI bug, or a bug in one of the applications, try to make a screen shot.
    22   1. If this is a crashing bug, i.e. the system popped up an alert notifying you that the application encountered a problem and can't continue, press the ''Debug'' button. This will open a Terminal window with gdb (the GNU debugger) running in it. Enter the command `bt` at the prompt to produce a back trace (aka stack trace or stack crawl). Copy the complete Terminal output (including the part before you entered the `bt` command) and attach it to the ticket.
     22  1. If this is a crashing bug, i.e. the system popped up an alert notifying you that the application encountered a problem and can't continue, a crash alert offers you several options. You can either save a report or write a core file (both saved to the Desktop) that you can then attach to a ticket.
    2323
    2424 == Server Bugs ==
    2525
    26 When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and a gdb session will be started, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and gdb output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.[[BR]]
    27 Save for everything being more ugly and inconvenient basically the same applies as for [#ApplicationBugs application bugs]. Most importantly procure a back trace (`bt` command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.[[BR]]
    28 Depending on what exactly crashed, you can try to save a crash report on the Desktop with `save-report` and then press the power button once to try shutting cleanly down.
     26When vital servers like the app server, the registrar or the input server crash, you won't see the usual crash alert. Instead the whole screen will be cleared white and the Debugger will be started in text-mode, its output appearing directly on screen. Likely you will still be able to move the mouse, which will overwrite the white and Debugger output on screen. Applications still running (like ProcessController or the clock in the Deskbar) might also draw over the debugger output on screen.[[BR]]
     27Besides everything being more ugly and inconvenient, basically the same applies as for [#ApplicationBugs application bugs]. Most importantly procure a back trace (`bt` command). You may need to take a picture of the screen with a digital camera, since you won't be able to copy the text anywhere.[[BR]]
     28Depending on what exactly crashed, you can try to save a crash report on the Desktop with `save-report` or `write-core` for a core file, and then press the power button once to try shutting cleanly down.
    2929
    3030 == Kernel Bugs ==