Daniel Pettersson

Hello and thank you for your bug report. A similar issue was recently solved in dape. Which version of dape and gdb are you using? If you are not using...

@MatthieuHAMEL this looks like an gdb bug. If I would have to guess its probably when resolving the printable value/name for `myVector` by the way of some script like `/usr/share/gcc-/python/libstdcxx/v6/printers.py`....

Excellent job @MatthieuHAMEL! I could not see a bugreport upstream, so I went ahead and created one. https://sourceware.org/bugzilla/show_bug.cgi?id=33594

This has now been fixed upstream in (Rust and libstdc gdb printers) I dont' know when the changes will land on debian's packaging of libstdc. I am guessing it will...

Hey! I am note sure if it's a typo in the issue but if you are specifying another python then the one under path it should be `command` not `comment`...

Strange it looks like `dape-cwd-fn` is returning nil. I don't think it will fix your issue but you seam to have an older version of dape then what is available...

Hey and thank you for the bug report. What version of dape and Emacs are you using, and does `M-x package-recompile dape` fix the issue?

Hey! `dape` does not support Emacs versions older then 29.1. I would suggest you upgrade Emacs, lots of nice things has been introduces since 28.3 :)

Hello! Somewhat confusingly the interactive input to `dape` i.e. "Run adapter: ..." differs a bit form non interactive. With interactive use (when you invoke dape as a command) Dape takes...

Thanks for the kind words, and sorry for the delay! This should work: ```emacs-lisp (defun debug-my-thing (argument) (interactive "sDebug my thing for argument: ") (dape `(command "python" command-args ("-m" "debugpy.adapter")...