windows - WinDbg session variables - Aliases vs. User-Defined Pseudo-Registers -


i need hold specific value (a string, exact) throughout lifetime of single windbg session.

the reason that, need address variable in few places throughout lifetime of windbg session (through .if statements, exact), , want defined @ startup of session - using argument that'll passed. can't undefined or disposed - must able address in point in debugging session, , of course don't want risk might redefined.

i thinking of using file purpose, or shared memory, prefer solve using windbg scripting. if it's possible, it's more elegant solution.

i've done reading online on matter , issue couldn't find reference differences between aliases (defined as command) , user-defined pseudo-registers (the registers in range $t0..$t19, accessed using r command) described. couldn't find understand use cases each.

the seemed me aliases better option, due fact can named, in contrast user-defined pseudo-registers have set names (wasn't sure regarding how pick "right" registered, minimize possible collisions other scripts might use it, or there difference @ all).

am missing here? should use in case, or both unsuitable situation?


Comments

Popular posts from this blog

resizing Telegram inline keyboard -

command line - How can a Python program background itself? -

php - "cURL error 28: Resolving timed out" on Wordpress on Azure App Service on Linux -