search

microsoftfeedback / WinDbg-Feedback

Public issue and feedback tracking for WinDbg Preview.
Creative Commons Attribution 4.0 International
47 stars 12 forks source link

Add a way to autoload extensions #32

Open cbiesinger opened 5 years ago

cbiesinger commented 5 years ago

With "classic" windbg, you can copy an extension DLL under the install directory.

With Windbg Preview, that directory seems to be made readonly (by the store installer, I guess). There should be some way to autoload extensions. Maybe a well-known directory in %USERPROFILE%, or something under AppData, or a setting.

ge0rdi commented 5 years ago

WinDbg preview looks for extensions in: %LOCALAPPDATA%\Dbg\EngineExtensions %LOCALAPPDATA%\Dbg\EngineExtensions32 (for 32bit DLLs)

You should be able to see those folders when you'll run .extpath in debugger.

Not sure if those paths are documented somewhere (it will be great if they were).

cbiesinger commented 5 years ago

Oh, thanks! But it doesn't work for me? With the extension from https://github.com/MicrosoftEdge/JsDbg: 0:000> !jsdbg No export jsdbg found 0:000> .load jsdbg The call to LoadLibrary(jsdbg) failed, Win32 error 0n2 "The system cannot find the file specified." Please check your debugger configuration and/or network access.

I don't see anything related in https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugging-using-windbg-preview either

cbiesinger commented 5 years ago

But setting %_NT_DEBUGGER_EXTENSION_PATH% did work for me (as did .extpath+, but that's not persistent. Maybe make a persistent setting for it?)