After having used WinDBG Preview for a few weeks now, I can say that it does present a lot of issues with symbol resolution. The amount of time I have wasted because it cannot load symbols is significant enough to possibly be a deal-killer.
To date, I have still never been able to get it to load symbols for a process that you attach to (as oppose to loading directly). You can explicitly set the symbol path to the location of the exe/pdb, and verify that symchk.exe says they match, but WinDBG Preview still fails.
-
-
This is especially problematic because it means you cannot use WinDBG Preview as a JIT debugger, because it literally can't ever show you source code for the thing that Windows JIT-loaded.
Show this thread -
(and WinDBG Preview specifically says that the PDB can't be loaded because it's mismatched, even though symchk.exe says the PDB _does_ match).
Show this thread
End of conversation
New conversation -
-
-
Though Casey it seem that some one love it because is way more customizable using custom extensions. Let's gave them the time maybye when it's not a preview anymore some of the problems are solved, and of course given they are Microsoft they will brake what is working
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.