.net - Visual Studio - Runtime impact of conditional and disabled breakpoints -
Spending a bit of time thinking that why my app was running a special scenario with the attached debugger, I came to know Due to this being a conditional breakpoint (whose position was never found) it seems reasonable because the CPU will indicate the breakpoint and will need to evaluate the situation before allowing VS to continue. These infections should be expensive.
I think a breakpoint has not been implemented in the code path, there is no runtime effect.
So my question is doubled:
>
Of course if I do not mean anything mentioned above, please point me to the right direction.
The cost of conditional breakpoint is difficult to assess. Assessment of expression in conditional breakpoint is exactly the exact same words as you typed it in the clock or instant window. The expression of this nature is not actually executed in the client program, but rather the language is handled by the specific expression evaluator. It is actually not possible to profile these types of evaluation in a meaningful manner
However, I can list some things which are known slow in debug window eval
- Function call: They are the slowest thing because you can call functions
- String comparison: Under the hood, they are encoded for the flick
Disabled Breakpoints for no, no, they run the application Do not affect the area.
Comments
Post a Comment