I have tried to open multiple memory windows but I can't.
I tried to find resolution for this on windbg help and on old version it is possible, however on new version I can't find how to open multiple memory windows. Please help me!
I have tried to open multiple memory windows but I can't.
I tried to find resolution for this on windbg help and on old version it is possible, however on new version I can't find how to open multiple memory windows. Please help me!
Copyright © 2021 Jogjafile Inc.
As far as I do WinDbg debugging, I don't use memory windows at all. And maybe you shouldn't use them either. Why?
When doing debugging for clients, they pay me for that. What they get is a complete protocol of my work. That means, I basically a
.logopenis my first command and a.logcloseis my last. Doing anything outside the command window will not be recorded and someone else cannot reproduce the debug session any more (most of my work involves crash dump analysis, not live debugging). Such a log file is also useful for myself, e.g. I can construct a summary of all the commands I used for debugging this kind of problem and I can offer a follow-up workshop for the employees of the company.Thus, the memory window is useless and I use the
db,ddand related commands instead.With that statement made, I don't see any issues in WinDbg 6.12 through 6.3.9600. Note the breaking change in version numbering.
WinDbg Preview (the one from the app store) does not support multiple memory windows right now. It is - well - still a preview. It seems that memory windows have not been important enough for Microsoft employees either.