About using the debuggers

[mortang2410]

Hi. I am new to Doom Emacs, though I had used Emacs beore years ago. I see that using the various debuggers in Doom Emacs is somewhat confusing (at least for me I suppose). The included documentation for :tools debugger is rather sparse with unwritten parts. It mentions both dap-mode and DAPE, which are two different things. So I am sharing some of what I have figured out through trial and error, and I hope people could tell me whatever I get wrong. More tips would also be appreciated. Hopefully it will help others, and the documentation will be filled out soon.

• How to use debugger to debug emacs lisp:
  • Set debug-on-entry for a function to debug and then run/eval any elisp expression. Unfortunately debugger doesn't correspond with source (edebug uses source). Also don't turn on debugger mode on the source file (it is for the debugger backtrace buffer). In the debugger backtrace buffer, press d or j to continue. We can backtrace-toggle-locals to show locals of a specific function / context. For some limited symbols we can use backtrace-help-follow-symbol to jump to source.
• How to use edebug to debug emacs lisp:
  • Need to set edebug-instrument-defun-on for functions you want to monitor. Then run/eval any expression with gR. edebug works like debug above, but also shows which line of code in the source you're on. Press n in the source file to make one more step. Press d in the source file to see backtrace buffer, where backtrace-toggle-locals also works. Press q in source file to quit edebug.
• How to use DAPE to debug C/C++:
  • Doom docs say +lsp :: is a deprecated flag along with dap-mode and dap-ui, and that it requires :tools lsp (not compatible with Eglot). I am not sure what this means, but I suspect that dap-mode and dap-ui should no longer be used. And the :tools debugger perhaps used to be :tools debugger + lsp (but is no longer). Nowadays we enable both debugger and lsp under :tools in init.el.
    • Eglot is Emacs' built-in LSP client, and it seems to be an alternative to lsp-mode. Only one can be active at a time for any programming language. Check doom docs for each language to see how to choose which with flags.
  • Run dape with M-x in a C file, and you will be asked for the "adapter" command. Example: assuming the compile command is cc -g main.c -o main.out (output with debug symbols), a correctly formatted adapter command is
    lldb-dap :program "/Users/John/programming/C_testing/main.out" :cwd "/Users/John/programming/C_testing/" where you provide the correct :program and :cwd (current working directory). Remember to set breakpoints with dape-breakpoint-toggle.

[Steve-Cooley]

Yeah, I've never gotten debugging to work. Thanks for looking into this, even though I wasn't quite able to get it to work for me. I am using eglot. I didn't know it was incompatible with dap. Or is it dape?

This probably won't help anyone, but what I've done for Python:

• install debugpy
• ensure node is installed
• enable (debugger + lsp) in the init.el (apparently the +lsp is deprecated? or is that for each :lang?)
• There's some python specific code that the documentation recommends adding to the config.el. So I added that. I'll paste it below.
• open a python file i'd like to debug
• start the debugger with spc o d
• get a prompt to "run adapter:"
• do some googling, ask CGPT, (CGPT is not useful here)
• ask deepwiki, more below
• give up and either use another editor or use print debugging.

deepwiki actually said that you need to create an adapter file in $DOOMDIR/debug-adapters/, and gave an example of an adapter:

(:type "python"  
 :request "launch"  
 :name "Debug Python Script"  
 :program "/path/to/your/script.py"  
 :cwd "/path/to/your/project"  
 :console "integratedTerminal")

Actually, deepwiki gave several examples of debug adapters for Python, one for single file scripts, one for modules, etc. I felt like it might be hallucinating/confabulating, so I came here!

This is free software, so I don't want to sound like I'm making demands, but it really would be nice to have some better documentation for the debugger in Doom. Unfortunately, those that are qualified probably don't have time, and the rest of us... are just not qualified. 😄

Maybe some Emacs guru will be kind enough to chime in sometime down the line. 😄

edit:
The documentation recommends adding this to config.el for Python debugging:

(after! dap-mode
  (setq dap-python-debugger 'debugpy))

edit2:
OK, the above code (found in the :debugger page of the documentation) must be out of date, because it references dap-mode, and dape has replaced it.