Timeline for A curious case of Visual Studio 2010 debugger(it can not hit a break point)
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2011 at 11:58 | comment | added | MattDavey | @CuiPengFei yes, even though other break points are hittable (those lines of code may not have been optimized) | |
| Apr 22, 2011 at 1:38 | comment | added | Cui Pengfei 崔鹏飞 | @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. | |
| Apr 21, 2011 at 17:02 | comment | added | forsvarir | @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. | |
| Apr 21, 2011 at 15:44 | comment | added | MattDavey | @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. | |
| Apr 21, 2011 at 14:22 | comment | added | DWRoelands | It sounds as though your Release Mode configuration is set to not include debug information. Check the Advanced Compile Options in your Project Settings. | |
| Apr 21, 2011 at 13:18 | comment | added | Cui Pengfei 崔鹏飞 | Yes, I know that'll make the break point hittable. But I just want to know why it's not working in Release mode. | |
| Apr 21, 2011 at 13:17 | comment | added | forsvarir | That's not really an answer as to why isn't not being hit, it's how to make it behave as expected.... | |
| Apr 21, 2011 at 13:14 | history | answered | DWRoelands | CC BY-SA 3.0 |