This is a handy tip from Jim Beveridge. It shows you how to add to the list of native function calls that the debugger steps over rather than into when you're debugging in various flavours of Visual Studio.
I wonder if the debugger picks up changes to the registry key whilst VS is running, if so there's scope to build a little add-in that lets you add to the list from within VS...Step over library code when debugging C++ in Visual Studio
2 Comments
Leave a comment
Follow me on Twitter: @LenHolgate
I have other blogs...
The Server Framework - high performance server development- Lock Explorer - deadlock detection and multi-threaded performance tools
- l'Hexapod - embedded electronics and robotics
- MegèveSki - skiing
I also write about...
- .Net
- Books
- C++ Tips
- CC.Net
- CLR Hosting
- CORBA
- Continuous Integration
- Debugging Tools
- Dumbing down is dumb
- ENet
- Geek Speak
- General
- Get a life
- Holiday Pictures
- Java
- Linux
- Lock Explorer
- Managed XLL
- OLEDB
- Rants
- Refactoring
- Reprints
- Role Playing
- Socket Servers
- Sound and Vision
- Source Code
- Testing
- Way back
- Winsock Registered I/O
- x64
It is picked up by VS at each init of a debugging session (same as autoexp settings). So it should be modifiable from within VS.
Cool. Now, I wonder how I can find the time to investigate that...