.logopen
is not the answer, because it lets the command output to the windbg console.
For example, !sosex.dumpgen 2
produces a helluva lot of output, which I do not want to see in the debugger console. Right now I am using the following:
.shell -i- -ci "!dumpgen 2" cmd /c more > D:\tmp\dumpgen2.log
My problem is that the more
command is interactive and requires user input after outputting certain amount of data. This is a huge problem for me.
One solution could be running the debugger itself non interactively with a script and use the .logopen command there.
I wonder if I could achieve what I want while:
.shell -i- -ci "!dumpgen 2" findstr "^" >D:\tmp\dumpgen2.log
^
will find the beginning of any line, so it should be a 1:1 copy.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With