Closed Zero3K closed 2 months ago
Seems possible to do via the command line options available to WinDbg and WinDbg Preview:
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/windbg-command-line-options https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/windbg-command-line-preview
In the meantime, you can already do this with WinDbg Workspaces. Configure the symbol and source paths for a particular VM and then save that configuration to a workspace for that VM. When you attach to that VM again in the future, load the workspace associated with it.
I'm going to hold off on implementing this enhancement for now because it can already be accomplished in WinDbg and feels like it's a bit redundant and outside the scope of VirtualKD-Redux.
In WinDbg, this is a reason why workspaces were created. Just create and use a different workspace for each VM you have:
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/using-workspaces
It would be nice if a user could set the symbol and source paths for a VM so that way WinDbg will always be looking for the proper PDBs and showing the correct source code.