Using Bugsaur¶
The debugger window is one screen with eight panels. This section explains each of them, one page at a time.
If you have not seen the window yet, start with Your First Debug Session — it gets you to a stopped program in a few minutes. Come back here when you want to know what everything does.
The panels¶
| Panel | Shortcut | What it is for |
|---|---|---|
| Debugger UI | — | the window as a whole: zones, focus, layout |
| Breakpoints | Ctrl+B | where execution should stop |
| Stepping | — | moving through the program |
| Call Stack | Ctrl+C | how execution got here |
| Threads | Ctrl+T | what else is running |
| Variables | Ctrl+V | state in the selected frame |
| Watches | Ctrl+W | expressions kept across stops |
| Evaluate | Ctrl+E | one-off questions |
| Inspector | Ctrl+I | one value, in full |
| Logs and Diagnostics | Ctrl+L | what the machinery is doing |
Two things worth knowing early¶
The window is keyboard-first. Exactly one panel is active for the keyboard at a time: its tab is highlighted and its body is framed. Tab and Shift+Tab cycle through panels; Ctrl plus the panel's letter jumps straight to one. Inside a panel, J / K and the arrow keys move the cursor. Full map: Reference → Keyboard Shortcuts.
The debugger does not own your breakpoints. They belong to the editor and
live in .bugsaur/breakpoints.json. You can look at them in the window, but you
set and clear them in your editor. The reasoning is on the
Breakpoints page.