windbg - Commands that only affect the local debugger -


when doing remote debugging, commands affect local debugger (the debugger on command typed). examples are:

.wtitle .cls .browse .cmdtree 

at moment these looking ui related commands. there more commands executed on local debugger?

my research effort:

  • i googling list, maybe search terms common or don't them right.

  • i have tried finding reference in windbg (.hh) itself. fact not documented on affected commands found far.

i aware asking favorite external tools or reference. if think off-topic, vote close.

all debugger processing, including extension execution, done in core debugger process. 99+% of commands need go debugger engine (the initial debugger instance) commands run on remote debugger indeed few ui related commands.

i call out 1 pair of commands interesting on topic commonly used remote debugger:

.srcpath sets "source code path" in debugger engine. debugger engine source information if it's needed - example, if debugger extension wants source code.

.lsrcpath (l - local) sets "source code path" in remote debugger. path used in windbg (and cdb\kd also) pull source files in ui.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -