Is there a macro that does it? Which DTE objects to use?
相关问题
- how to call a C++ dll from C# windows application
- Pass custom debug information to Microsoft bot fra
- efficiently calling unmanaged method taking unmana
- I want to trace logs using a Macro multi parameter
- How do I identify what code is generating “ '&
相关文章
- Macro expansion in elixir: how to define 2 macros
- How do I get to see DbgPrint output from my kernel
- How to import macros in Rust?
- Advanced profiling is unavailable for the selected
- Can't Inspect Variables When Debugging .NET As
- What is the difference between glibc's MALLOC_
- C++: Callback typedefs with __stdcall in MSVC
- Embedding a program's source code into its bin
There is a macro, but I tested it only with c#.
Like Constantin's method... This seems like windbg territory.
Since you have the cpp, (even if you didn't you could script something to get by), it should be no problem to use logger part of the debugging tools for windows... it's a very handy tool, shame so few people use it.
logger debug's C/COM/C++ easily, with rich symbolic info, hooks/profiling/flexible instrumentation;
One way to activate Logger is to start CDB or WinDbg and attach to a user-mode target application as usual. Then, use the !logexts.logi or !logexts.loge extension command. This will insert code at the current breakpoint that will jump off to a routine that loads and initializes Logexts.dll in the target application process. This is referred to as "injecting Logger into the target application."
I don't know what DTE functions to use, but you could very simply record a macro that could pretty much do it:
Now just run this over and over (ctrl - shift P repeatedly) until you reach the end of the file.
If you have namespaces, then change 4. to:
This kind of thing can be infinitely modified to suit your codebase
(This is not quite what you're asking for, but almost:)
You can put a breakpoint on every member function of a class in Visual Studio by bringing up the New Breakpoint dialog and entering:
See http://blogs.msdn.com/b/habibh/archive/2009/09/10/class-breakpoint-how-to-set-a-breakpoint-on-a-c-class-in-the-visual-studio-debugger.aspx for more details.
Put this at the top of the file:
then insert DEBUG_BREAK in the beginning of every function, like this:
When you no longer want the debug breaks, comment the line
at the top of the file.
Here's a quick implementation of 1800 INFORMATION's idea: