Twitter | Search | |
Matt Warren
help me out, what are the ways that you've debugged a .NET program (Framework/Core)? - Visual Studio - JetBrains Rider - VSCode/OmniSharp - WinDBG & SOS - CLR Managed Debugger (mdbg) Any I've missed? (proper debugging only, 'print' statements don't count!!)
Reply Retweet Like More
[RG] 17 Aug 18
Replying to @matthewwarren
Windbg, sos, perfview, CLR profiler, Ants profiler, DebugDiag, etc.
Reply Retweet Like
Matt Warren 17 Aug 18
Replying to @rupreetg
Thanks, that's a useful list
Reply Retweet Like
ух как печот 17 Aug 18
Replying to @matthewwarren
You underestimate the power of debugging prints! 😁
Reply Retweet Like
Matt Warren 17 Aug 18
Replying to @fixer_mm
Oh yeah, I agree they're very powerful (it's just that I'm writing a post about the .NET debugging APIs, so I wanted to limit the list to tools that use that)
Reply Retweet Like
Kris Mok 18 Aug 18
Replying to @matthewwarren
If you count SSCLI then there was GDB+SOS in the big picture, too
Reply Retweet Like
Matt Warren 18 Aug 18
Replying to @rednaxelafx
Interesting. I guess that VS didn't support debugging *managed* code in SSCLI, is that right?
Reply Retweet Like
Jared Parsons 18 Aug 18
Replying to @matthewwarren
LLDB + SOS on Ubuntu
Reply Retweet Like
Matt Warren 18 Aug 18
Replying to @jaredpar
Thanks. Seems that's a popular combo
Reply Retweet Like
Jiří Činčura ↹ 17 Aug 18
Replying to @matthewwarren
Does throwing exceptions (instead of print statements) count?
Reply Retweet Like
Matt Warren 17 Aug 18
Replying to @cincura_net
Not really, although it is an interesting technique! 😀 Was mostly looking for actual debugging tools
Reply Retweet Like