Break-bp-continue - Good idea, but could definitely surprise people. We're going to add this as an experimental setting, hopefully in the next release.
-
-
Replying to @aluhrs13 @cmuratori
Breakpoint hotkey - I actually wasn't aware VS had that hoteky, interesting that Ctrl+B is used for something other than bold. We'll look at adding this soon.
2 replies 0 retweets 0 likes -
Replying to @aluhrs13 @cmuratori
Unresolved - This is pretty deep in the debugger engine and difficult to fix. We want to rework some of how breakpoints work, but it's a large investment for the value so it's not high up on our backlog. Will look at if there's something we can do in the UI layer to compensate.
1 reply 0 retweets 0 likes -
Replying to @aluhrs13 @cmuratori
Source/ASM stepping - We've used almost all the "easy" default hotkeys, so I don't want to take up three more (6 if you include reverse versions). What if we added one to easily swap Source/ASM mode?
2 replies 0 retweets 0 likes -
Replying to @aluhrs13 @cmuratori
Registers window - Definitely not the best window right now. Not a high priority to fix at this point since the 'r' command tends to be easier for most people and cases, but we're aware of the pain.
1 reply 0 retweets 0 likes -
Replying to @aluhrs13 @cmuratori
PDB hunting - I'd be interested in more examples or suggestions, but this is something we likely won't change. Symbol loads are already time consuming, and we avoid adding things that complicate it. Symopts enable a lot of options that might help? - https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/symbol-options …
2 replies 0 retweets 0 likes -
Replying to @aluhrs13 @cmuratori
Window layouts - UI and target settings were coupled in legacy WinDbg, but we've decoupled them in WinDbg Preview in the way you've described. Can you elaborate what you mean by this part?
2 replies 0 retweets 0 likes -
Replying to @aluhrs13 @cmuratori
File menu – We’re aware it’s a bit jarring for experienced users, but it’s much more friendly to new users.
2 replies 0 retweets 0 likes -
-
Replying to @cmuratori
Poor phrasing on my part (I blame tweet length restrictions). Friendlier to non-hardcore-developers might be more accurate? It's definitely an area I've kept an extremely close eye on since we thought it'd be pretty controversial.
1 reply 0 retweets 0 likes
I perhaps assumed that non-hardcore-developers would not be using WinDBG in general :)
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.