-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
error in process sentinel: dap--buffers-w-breakpoints: Wrong type argument: markerp, nil #796
Comments
it happens even without a launch.json, chosing instead a template like this:
|
at first inspection it seems related to this commit: ed360fd . I'll try rolling back dap-mode version before it and see if it works. |
Yes, rolling back to the previous commit actually solve the problem. @sfavazza and @sfavazza-duagon do you guys have any insight on what could be the issue? or how could i help you debug the problem? |
I am not sure what it could be, I cannot reproduce it. I am sure @vibrys tried the latest package version. I checked it myself and I did not observed changes in the code affecting my contribution. Judging from the code the most probable cause of error I can think of is a change in the object returned by I suggest you step-debug through it and see when exactly the |
So, I am not sure about what triggered this, but after restoring the old package version (20240611.1356) and running an "Update packages" (i'm running the spacemacs distribution) everything seems to work, it only gives me that error if i don't set a breakpoint in the source code (understandable). Maybe I could just add a clarifying message, if I'm able to debug it better i'll post a little PR. |
Sorry, it seems that debugging the debugger is a bit too far from my skill set. Still a better error message would probably be a good idea. |
after
M-x dap-debug
is called onlaunch.json
file below, I get following error:launch.json:
then, here's the stacktrace with
M-x toggle-debug-on-error
:versions are:
please help
kind regards,
Matt
The text was updated successfully, but these errors were encountered: