New blog post: WinDBG Preview is actually a reasonable everyday debugger! This is very good news for anybody looking to move away from Visual Studio 20xx:https://caseymuratori.com/blog_0033
-
Show this thread
-
Replying to @cmuratori
The official place to get feedback to us is the Feedback Hub - http://aka.ms/dexex . That's what we use for features when we aren't sure what most people want, there's a few things that should go there so others can upvote them. Don't hesitate to keep tweeting at me though.
1 reply 0 retweets 1 like -
Replying to @aluhrs13 @cmuratori
Tweetstorm incoming for all your targeted feedback incoming.
1 reply 0 retweets 0 likes -
Replying to @aluhrs13 @cmuratori
CTRL+SHIFT+F5 - Should be fixed in an upcoming release (for user-mode, thinking through kernel-mode). I'm not keen on F5 restarting though. It makes sense in VS, but in WinDbg it could lead to some really inconvenient restarts if you don't realize you're at the end of execution.
2 replies 0 retweets 1 like -
Replying to @aluhrs13 @cmuratori
Keyboard bindings - Throw in Feedback Hub please. I like the idea, but haven't seen a enough of an appetite to prioritize it at this point. We have a feature coming soon that'll make running scripts less painful (for JavaScript scripts), but not keybind them.
2 replies 0 retweets 1 like -
Replying to @aluhrs13 @cmuratori
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.
2 replies 0 retweets 1 like -
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
Modal keys are usually a bad idea. You want the muscle memory to just work, you don't want to first have to remember/check whether you're in ASM or source mode. Adding user-bindable keys would solve the problem, since you could leave them unbound by default?
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.