-
Notifications
You must be signed in to change notification settings - Fork 26
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
Watch Variables can't be resolved after a Debugging Restart and Debugger does not start #26
Comments
I was able to reproduce this. Please try following package to check the fix:
|
Hello, the Bug is bassically gone.
Probably there is a issue in the parsing of the value. For my understanding it should look like:
When the value is not defined resp. assigned it looks like:
It think it would be event better and more consistent when the value is not defined / assigned to show just:
This corresponds to the same value when the Debugging has been stopped. Best regards, Daniel... |
I am connecting watch and peek features of debug adapter to "examine" command of bashdb. It will return those "declare .." words if watch is "DebPath", not "$DebPath". However, I noticed that the expression name "DebPath" is redundant in response, so I will remove it so that only value is shown in single quotes. I will need to properly document how watch works, since i do not want to make any workarounds related to the problem at this point... |
Is this fix already public available in Form of a Release? |
v0.0.7 should contain all the fixes I could do for now. It is published to VS Code marketplace... |
Hallo,
I have noticed that when I add a Variable to the Watch Window the Debugger is not able to resolve this Variable when I restart the Debugger and the Debugging will not be started.
My concrete use case:
1.) Start Debugger
2.) Add Variable to Watch Window -> no problem, variable value will be resolved
3.) continue debugging (some steps)
4.) restart the debugger -> debugger can't resolve variable and does not start debugging
In the Watch window appears the following error message:
The text was updated successfully, but these errors were encountered: