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
Oleg Mihailik Aug 17
Replying to @matthewwarren
SharpDevelop and DNSpy — useful (but lame) to debug stuff in production.
Reply Retweet Like
Jiří Činčura ↹ Aug 17
Replying to @matthewwarren
Does throwing exceptions (instead of print statements) count?
Reply Retweet Like
Matt Warren Aug 17
Replying to @cincura_net
Not really, although it is an interesting technique! 😀 Was mostly looking for actual debugging tools
Reply Retweet Like
Matt Warren Aug 17
Replying to @486timetable
I'd forgotten about DNSpy, thanks for the reminder! You get bonus points for that because it uses ClrMD and the CorDebug API!
Reply Retweet Like
Joseph N. Musser II Aug 17
Replying to @matthewwarren
Visual Studio with dotPeek as symbol server to step into third party code, set breakpoints and and view locals.
Reply Retweet Like
David Xavier Aug 17
Replying to @matthewwarren
Omnisharp visual studio
Reply Retweet Like
Sebastian Solnica Aug 17
Replying to @matthewwarren
lldb + sos 😬
Reply Retweet Like
Matt Warren Aug 17
Replying to @lowleveldesign
Nice, I assume this is for debugging on a non-Windows OS?
Reply Retweet Like
Matt Warren Aug 17
Replying to @jnm236
Cool. Out of interest, what does dotPeek give? What use that for the symbol server?
Reply Retweet Like
Peter Tiedemann Aug 17
Replying to @matthewwarren
VS and Rider only, apart from a few tries in vs code
Reply Retweet Like
Christophe Nasarre Aug 17
Replying to @matthewwarren
- my own tools with ClrMD - perfview (exceptions, finalizers, memory/CPU)
Reply Retweet Like
Matt Warren Aug 17
Replying to @chnasarre
Nice, I'd not really thought about using 'PerfView' for debugging, interesting idea!
Reply Retweet Like
Sebastian Solnica Aug 17
Replying to @matthewwarren
Yes, unfortunately sos does not work with the latest version of lldb, but it’s still something :)
Reply Retweet Like
Matija Grcic Aug 17
Replying to @matthewwarren
Mainly WinDbg & SOSEX. But I've used the CLR Profiler, MemAnalyzer , Mex , NetExt , Psscor4 , ProcDump .
Reply Retweet Like
Rupreet Gujral Aug 17
Replying to @matthewwarren
Windbg, sos, perfview, CLR profiler, Ants profiler, DebugDiag, etc.
Reply Retweet Like
Matt Warren Aug 17
Replying to @matijagrcic
Thanks, that's a great list!
Reply Retweet Like
Matt Warren Aug 17
Replying to @rupreetg
Thanks, that's a useful list
Reply Retweet Like
Matija Grcic Aug 17
Replying to @matthewwarren
Not a problem, each serves some a purpose but the main thing is to have proper symbols and architecture. ProcMon is also powerful for non intrusive production debugging if you give it the dbghelp.dll and symsrv.dll, which you extract from WinKit msi.
Reply Retweet Like
Stuart Blackler Aug 17
Replying to @matthewwarren
Not sure if it counts as debugging but we log all telemetry info to elastic with our logs, across microservices, so we get method calls throughout the stack for free. Kinda like “we got here and we took this long”.
Reply Retweet Like