Adding a breakpoint at line 3 with dap-breakpoint-add and running dap-debug.
This is part of multiple other errors in the interaction between dap-mode, lsp-mode, and treemacs as killing the session and re-running dap-debug produces other messages, without stacktraces even if deubg-on-error is turned on, and the dap UI gradually activates with the left and right vertical bars displaying the dap-ui-breakpoints and dap-locals buffers.
treemacs--do-expand-generic: Wrong type argument: integer-or-marker-p, nil
Error running timer ‘dap-ui-locals--refresh’: (wrong-type-argument integer-or-marker-p nil)
Debug session process exited with status: killed
treemacs--do-expand-generic: Wrong type argument: integer-or-marker-p, nil
treemacs-expand-node: Wrong type argument: integer-or-marker-p, nil
treemacs-expand-node: Wrong type argument: integer-or-marker-p, nil
I've encountered this with a simple ruby script:
Adding a breakpoint at line 3 with
dap-breakpoint-add
and runningdap-debug
.This is part of multiple other errors in the interaction between dap-mode, lsp-mode, and treemacs as killing the session and re-running
dap-debug
produces other messages, without stacktraces even ifdeubg-on-error
is turned on, and the dap UI gradually activates with the left and right vertical bars displaying thedap-ui-breakpoints
anddap-locals
buffers.My spacemacs config is here: https://gitlab.com/sdwolfz/dotfiles/-/blob/master/.spacemacs and I'm running emacs in the terminal.
Let me know if you need more information. I was unable to debug it further.