The Scenic App depends on a complex software stack. As such, bugs can occur in any of the stack's components. Bugs will typically emerge from one of the following components:
- The Scenic App itself
- The Scenic Core websocket server
- The Switcher engine
Relevant debugging information about each of these components can be produced by following the steps below. Please include as much information as possible when submitting your bug report.
The following debugging steps may require administrator privileges.
Getting the Scenic App Log
The Scenic App log is accessible from the Chrome/Chromium browser's DevTools. Consequently, you should :
- Open the Chrome DevTools
- Open the
- Right-click in the
- Select the "Save as..." option in the contextual menu
- Send the saved file to the maintenance team
Getting Scenic Core and Switcher's stack trace
In order to debug this stack you should :
- Install the GDB software
- Recompile Switcher in
- Rebuild Scenic Core (optional)
make gdb-debugin order to start Scenic Core with GDB
runin the GDB prompt
When Scenic Core is launched, you should be able to connect Scenic App to it. Now is the time to reproduce your bug.
When a bug is thrown, the GDB prompt will freeze. You should then :
bt fullin the GDB prompt to display the full stack trace
quitin order to exit GDB
- Get the log file saved in
- Send this file to the maintenance team
Adding information about your hardware
Information about your hardware may be useful for the maintenance team and can potentially accelerate bug resolution requests. All relevant information about your hardware can be produced with the following command :
sudo lshw > system-specs.txt
Please include this file with your bug report.