Debugger
Local engine connection
The debugger workspace is open. Program execution needs GDB and the Python server on your PC. The public website has no running engine. Start server.py from the downloaded source; it opens an authenticated local workspace automatically.
Open by path
Selected and dropped files open from a local temporary folder. Use the original path for programs with DLLs or configuration files. Maximum 128 MiB.
Disassembly
CPU| Address | Bytes | Instruction |
|---|
No target
Registers
HEX—
Memory
Memory search · value inspector
Searches only the currently loaded memory range.
Click a byte to interpret values starting at that address.
—
Call stack
0 FRAMES—
Breakpoints
●No breakpoints
Threads · local variables
—Click a stack frame to inspect its variables and registers.
Event log
OutputCTF tools
Binary information · strings
Memory · register editing
Changes values in the stopped process, not the binary file. Select frame 0 to edit registers.
Target input · output
Compare recorded stops 0
Keeps the last 50 stops in tab memory. Reloading or switching language clears them. Viewing a record does not rewind the process.
| Register / address | A | B |
|---|
Reports use record B. Review contents before sharing. Workspace files include the executable path and program arguments.
Notes
DBG Desk connects to GDB on your computer to inspect a real running program. Open an executable or attach by PID, then inspect instructions, registers, memory, and the call stack at a breakpoint. A Python local server and a compatible GDB are required. Files and debugging state are not uploaded to an external server.
Start with a small example and stop at main. F7 executes one instruction, F8 steps over a call, and F9 continues to the next breakpoint. Compare a function’s inputs and results to narrow down where a value becomes incorrect. The memory panel shows a stopped snapshot; it does not automatically establish object validity or diagnose the cause.
The debugger supports stopped-process memory and register edits and starting at the first instruction. Linux uses the web input panel; Windows uses a separate target console. File patching and reverse execution are not supported. Use the debugger for the relevant language for Python tracebacks and JavaScript exceptions. See the guides for investigation steps.