How can I make the Visual Studio debugger stop breaking at data breakpoints which are set to run a macro and continue?

Question

I'm running into an odd problem with Visual Studio 2005: I have a data breakpoint that's set to run a macro and continue (that is, I select a macro and check Continue Execution.)

Now, instead of silently running the macro when the value in the data breakpoint (tracepoint, really) changes, I first get a message box informing me that the breakpoint was hit, and the macro runs only after I hit OK.

The code I'm debugging is timing sensitive, so this makes it impossible to debug. Is there a way to disable the message box that pops up?

In response to comments: The macro itself can be empty, or it can be any of the Microsoft provided sample macros - it doesn't make a difference.

Answer 1

I do not have vs.net 2005 on my machine.
So, I am speculating here.

What is the line of execution?

Is it trying to evaluate a property?
Is a conditional breakpoint set when the property is read? (i.e. break when property is read?)

Try removing other breakpoints related to the current line of execution and add tracepoint again.

Answer 2

It does this for me as well. The behavior does seem somewhat different based on how you set the "Continue execution" option, so my suspicion is that this behavior (painful as it is) may be by design. Or it may be a bug, but in either case you may be stuck.

An alternative might be to use windbg or one of the other Windows debugging tools, which also support data breakpoints. They take a bit of getting used to and are not nearly as user-friendly as the Visual Studio debugger, but they're pretty powerful. The "ba" command creates a data breakpoint, and you can program the debugger to perform a particular command when the breakpoint is hit. This article has some good introductory information about these debuggers, and the Q & A section near the end has an example of how to perform an action when a breadpoint is hit.