.logopen This is not an answer because it allows the command to output windbg to the console.
For example, it !sosex.dumpgen 2creates a lot of output that I do not want to see in the debugger console. Now I am using the following:
.shell -i- -ci "!dumpgen 2" cmd /c more > D:\tmp\dumpgen2.log
My problem is that the command moreis interactive and requires user input after outputting a certain amount of data. This is a huge problem for me.
One solution may be the debugger itself is not interactive with the script and use the .logopen command there.
I wonder if I can achieve what I want so far:
- Performing this action from an interactive WinDbg session
- Using simple standard shell commands (which can also be cmd.exe or powershell.exe). I know that writing a small utility that simply translates stdin to stdout is trivial work, but I prefer not to.
source
share