You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps I'm just missing something obvious but there doesn't seem to be a good/easy/reliable way to run a process under windbgx with a specific environment set.
It appears that environment variables I set in the terminal before launching windbx do not actually get carried forward to the debuggee when I launch that from within Windbg. Perhaps this is because windbgx is a store application with its own weird behavior?
There's also no UI under "Launch Executable" for specifying environment variables.
This feels like such a common use case that I'm wondering if I'm missing a trick. In either case, not exposing this functionality in the UI feels like an omission
The text was updated successfully, but these errors were encountered:
Perhaps I'm just missing something obvious but there doesn't seem to be a good/easy/reliable way to run a process under windbgx with a specific environment set.
It appears that environment variables I set in the terminal before launching windbx do not actually get carried forward to the debuggee when I launch that from within Windbg. Perhaps this is because windbgx is a store application with its own weird behavior?
There's also no UI under "Launch Executable" for specifying environment variables.
This feels like such a common use case that I'm wondering if I'm missing a trick. In either case, not exposing this functionality in the UI feels like an omission
The text was updated successfully, but these errors were encountered: