Download to read offline
Uploaded byDror Helper
Debugging with visual studio beyond 'F5'
The document discusses effective debugging techniques in Visual Studio, emphasizing a structured approach to problem-solving. Key steps include reproducing issues, analyzing system states, and utilizing tools like the immediate window and tracepoints. It also highlights the significance of gathering relevant information and using Visual Studio's features to streamline the debugging process.
More Related Content
Similar to Debugging with visual studio beyond 'F5'
![[Ebooks PDF] download C Package 100 Knock 1 Hour Mastery Series 2024 Edition ...](https://cdn.slidesharecdn.com/ss_thumbnails/77950-250115210538-3185d3d2-thumbnail.jpg?width=640&height=640&fit=bounds)
More from Dror Helper
Debugging with visual studio beyond 'F5'
- 1. Debugging with VisualStudio Beyond ‘F5’ Dror Helper (@dhelper)
- 2. About.ME Consultant & softwarearchitect @ Practical Software Developing software since 2002 Clean Coder & Test-Driven Developer Pluralsight author Blogger: http://helpercode.com Twitter: @dhelper
- 3. Why I hatedebugging: It’s never planned Usually complicated Extremely frustrating Tend to be stressful Always time consuming
- 4. Why debugging consumesso much time?
- 5. There are 0b10types of developers
- 6. A practical approachto debugging 1. Reproduce the problem 2. Get to where the issue happens 3. Analyze the system state 4. Create hypothesis 5. Fix the bug 6. Verify your solution 7. Celebrate
- 7. Reasons to usethe debugger Gather information Prove hypothesis Check solution
- 8. Reproduce the issue Isit reproducible? Is it reproducible on my machine? What input caused the problem? When was the last time it worked? Answer those questions before continuing to the next step!
- 9. Get to wherethe issue is How to waste time: - Not knowing where we’re going - Running through all the code - Multiple reruns + long startup time
- 10. Immediate window Exception thrown Breakpoints Who can helpus get to the bug
- 11. Immediate window debug andevaluate expressions execute statements print variable values
- 12. Stop on exceptions Wecan tell Visual Studio to break whe - An exception is thrown and not handled - An exception is thrown * Reduce noise using exception type
- 13. Breakpoints Pause execution So Ican inspect my code • Always • Conditional • Trace* • Data (VS2019)
- 14. Data breakpoints New inVS2019 .NET Core 3.0 only! Value must be on the managed heap
- 15. Gathering information Understand allthe information Don’t waste time traveling your code Quickly find relevant information
- 16. Learn to useyour keyboard Reduce mental overhead Debug naturally
- 17. Tracepoints Special kind ofbreakpoint Log information instead of stopping Use text and existing variables
- 18. When to useTracepoints Huge data + iterations (LINQ) Multi-Threading Sync issues (up to a point)
- 19. Visual Studio’s toolwindows Simple – Stack, Watches, Exceptions, Breakpoints Advanced – Tasks, Threads, Modules
- 20. Make Object Id Distinguishbetween different instances Track an object even if it’s out of scope
- 21. Debugging parallel code Tracepointsfor ad-hoc logging Tasks/Threads to find Blocked/Deadlocks Parallel Stacks to understand flow
- 22.
- 23. Parallel Task &Parallel Stacks View the logical call, the logical call stack and the task/thread state
- 24. Understanding your data UseMake Object Id to follow specific instances Search for objects and properties in Watch windows (VS019) Format how your data is displayed - ToString - DebbugerDisplayAttribute
- 25. Edit & Continueduring Fix – Build – Run cycles Immediate window to avoid crash on exception Edit values to for and prove hypothesis Avoid restarting your debugger
- 26. Edit & Continue Makesure Edit and Continue is enabled! Check list of supported/unsupported changes https://github.com/dotnet/roslyn/wiki/EnC-Supported-Edits ... Or just try and find out
- 27. What we’ve learnt ReproduceAnalyze Hypothesis Fix Verify Better debugging Using Visual Studio capabilities A structured process of finding and eliminating bugs
- 28. Dror Helper |@ dhelper | http://helpercode.com Thank you!
Editor's Notes
- #7 Need to find better way to show the steps and where the debugger comes in
- #8 Never ever start your debugger without a clear idea of where to go and what to check
- #9 What happens if I can’t? - Help from you team
- #17 When you use the debugger you want it to be a simple intuitive experience which means you do not want o use the mouse, you need the keyboard, and without thinking which requires some practice, especially since duerring debnugging we too frustrated to learn new stuff
- #28 What cause it? When did it start? Inputs/env Get to the issue Gather information Why it happen? Prove!