Add instructions for WinDbg Preview. #199
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sanketj
reviewed
Aug 26, 2019
sanketj
requested changes
Aug 28, 2019
| @@ -13,7 +13,9 @@ JsDbg currently supports WinDbg and the Visual Studio debugger on Windows, and G | |||
|
|
|||
| 1. Download the [JsDbg WinDbg extension](https://aka.ms/jsdbg-windbg). (This extension changes infrequently because JsDbg extensions can be updated without updating the WinDbg extension. [Last update: Jan 30th, 2019]) | |||
|
|
|||
| 2. Copy jsdbg.dll into the `winext` folder located next your `windbg.exe` installation. Make sure to use the x64 version of the dll for 64-bit WinDbg, and the x86 version for 32-bit WinDbg. | |||
| 2. Extract the file somewhere and keep track of the directory. | |||
|
|
|||
| 2. Copy jsdbg.dll into the `winext` folder located next your `windbg.exe` installation. Make sure to use the x64 version of the dll for 64-bit WinDbg, and the x86 version for 32-bit WinDbg. | ||
| 2. Extract the file somewhere and keep track of the directory. | ||
|
|
||
| 3. Set the environment variable `_NT_DEBUGGER_EXTENSION_PATH` to the directory containing `jsdbg.dll`. Make sure you use the right version (amd64 vs x86) for the WinDbg version you're using. This will also work with [WinDbg Preview](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-using-windbg-preview). |
There was a problem hiding this comment.
Might be better to say: "Make sure you use the version (amd64 vs. x86) that corresponds to the WinDbg version that you're using."
| 2. Copy jsdbg.dll into the `winext` folder located next your `windbg.exe` installation. Make sure to use the x64 version of the dll for 64-bit WinDbg, and the x86 version for 32-bit WinDbg. | ||
| 2. Extract the file somewhere and keep track of the directory. | ||
|
|
||
| 3. Set the environment variable `_NT_DEBUGGER_EXTENSION_PATH` to the directory containing `jsdbg.dll`. Make sure you use the right version (amd64 vs x86) for the WinDbg version you're using. This will also work with [WinDbg Preview](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-using-windbg-preview). |
There was a problem hiding this comment.
Do you think we really need the sentence about WinDbg preview? Since these instructions should work for both the Win32 and UWP apps, I don't think we need to say anything specific about either.
| contact [[email protected]](mailto:[email protected]) with any additional questions or comments. |
IhostVlad
approved these changes
Jul 30, 2020
ghost
approved these changes
Apr 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/loading-debugger-extension-dlls
We could also remove the winext directory suggestion, since this will
work for both "legacy" WinDbg and WinDbg Preview.