-
Notifications
You must be signed in to change notification settings - Fork 3
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
Natvis and WinDbg Preview #1
Comments
the Natvis documentation is very sparse and only written for VS. I have developed and debugged it with VS so I can't really tell you how it's going to perform in other debuggers. Try to see if you can find some error log, in VS when it fails to parse something the entire natvis file refuses to load. |
I checked the logs, there is only one interesting error message in the log:
I started debugging for the executable, loaded the source code of the file. Then loaded thr Natvis script and executed it. But I am now unsure whether I have to set additional |
In VS you just have to drop the natvis into the project folder and it auto loads, in vscode you have to set it as "visualizer path" (and only a single one is supported) Loading it should be all that is needed to be done. Also did you compile your executable with the |
You are right, I was using dmd. I now tried ldc with the mentioned arguments and it seems to work. After executing the script the graphical representation of e.g. a string array in the "Locals" view changed. I can now immediately see that there are 2 elements within the string array. What I wonder, the actual string content is still not displayed. Only in the raw view I can see the number representation of the char (0x61 for the letter A). |
can you attach a screenshot and information you can find about the type? |
Is the Natvis script usable with WinDbg Preview (Windows 10 microsoft store)?
I tried to load the script during a debugging session and hit the script execute button but do not see any visual effect (e.g. representation of string arrays in the locals view).
The text was updated successfully, but these errors were encountered: