Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • 1
    That's not really an answer as to why isn't not being hit, it's how to make it behave as expected....
    – forsvarir
    Commented Apr 21, 2011 at 13:17
  • Yes, I know that'll make the break point hittable. But I just want to know why it's not working in Release mode. Commented Apr 21, 2011 at 13:18
  • 2
    @forsvarir This is a perfectly valid answer. In release mode the compiler is much more aggressive in the optimizations it makes, the result is that your view of the source code has little similarity to the compiled, optimized result.
    – MattDavey
    Commented Apr 21, 2011 at 15:44
  • 1
    @MattDavey: It really isn't an answer. In fact, your comment is more of an answer to the OP's question. They already stated the required configuration to reproduce the issue. They never asked how to fix it. They asked WHY it wasn't hit. This answer, gives a one line instruction, it doesn't give a reason for the issue.
    – forsvarir
    Commented Apr 21, 2011 at 17:02
  • 1
    @MattDavey: "the source code has little similarity to the compiled, optimized result". even though, other break points are hittable, only the one on the last line does not work. Commented Apr 22, 2011 at 1:38