How does a debugger work?

The details of how a debugger works will depend on what you are debugging, and what the OS is. For native debugging on Windows you can find some details on MSDN: Win32 Debugging API. The user tells the debugger which process to attach to, either by name or by process ID. If it is a … Read more

Accessing console and devtools of extension’s background.js

You’re looking at the wrong place. These console messages do not appear in the web page, but in the invisible background page (ManifestV2) or service worker (ManifestV3). To view the correct console open devtools for the background script’s context: Visit chrome://extensions/ or right-click the extension icon and select “Manage extensions”. Enable developer mode Click on … Read more

Debugging in Clojure? [closed]

There’s also dotrace, which allows you to look at the inputs and outputs of selected functions. (use ‘clojure.contrib.trace) (defn fib[n] (if (< n 2) n (+ (fib (- n 1)) (fib (- n 2))))) (dotrace [fib] (fib 3)) produces the output: TRACE t4425: (fib 3) TRACE t4426: | (fib 2) TRACE t4427: | | (fib … Read more

How can I make gdb save the command history?

Short answer: mkdir -p ~/.config/gdb echo ‘set history save on’ >> ~/.config/gdb/gdbinit Long answer: Command history is covered in the GDB manual, 22.3 Command History. Create a file $HOME/.config/gdb/gdbinit, and add the following line: set history save on You can set the number of past commands saved with the following. The command is described as … Read more