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.
-
-
hmm, maybe report it and hope they will fix it? I'm not sure if they are trying to appeal to Developers or Reverse Engineers or both?
-
It's more of a litmus test. If the thing can't match EXEs and PDBs, it's clearly not ready for prime-time. That's not the kind of bug you need to report, it's a canary in a coal mine kind of thing where you need to shelve it and come back in a year to see where they are.
- Show replies
New conversation -
-
-
WinDbg Preview and SymChk(and VS) use the same binary for symbol resolution and isn't different in launch and attach, so this is something I'd like to look into... Can you share the logs from View->Logs after symbol loading doesn't work? DM or email (ALuhrs @ microsoft).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Have you tried using ‘.reload /i <executable>=<base addr>,<size>’ after setting the .sympath? Always works for me, atleast in the legacy windbg..
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.