search

4d61726b / VirtualKD-Redux

VirtualKD-Redux - A revival and modernization of VirtualKD
GNU Lesser General Public License v2.1
777 stars 136 forks source link

WinDbg is busy for 20+ seconds when getting a backtrace #53

Closed Zero3K closed 9 months ago

Zero3K commented 9 months ago

Can VirtualKD-Redux be modified to fix that?

4d61726b commented 9 months ago

Backtraces (i.e. k command) should be instantaneous. What's the exact command you are issuing?

Zero3K commented 9 months ago

!analyze -v

4d61726b commented 9 months ago

That command does significantly more than just backtracing.

The reason it's so slow is likely because of symbol loading in WinDbg which is unrelated to functionality that VirtualKD-Redux provides.

Try issuing !sym noisy before performing !analyze -v. This might give a hint as to where the bottleneck is, assuming it's related to symbols.

4d61726b commented 9 months ago

I'm going to close this issue because I believe it's related to downloading symbols and not any functionality provided by VirtualKD-Redux.

If you have reason to believe it's related to VirtualKD-Redux, you can reply to this issue and we can discuss further.