> Crossed breakpoint means that the breakpointed line has no executable code > on it.
For multi-line function calls, it is really frustrating to not have picked the right line, start the debugger, then watch your app run past all breakpoints, only to find that the BPs were not understood in the first place. Can Ariadna equate breakpoints on multi-line function calls and method headers with the first executable line? Why can't I set either method header or method opening brace anymore to break on method entry? Can you understand why it's a PITA to first run and then have to figure while the app is busy that it's not stopping when you think it's supposed to? MSVC had a nice approach to this problem: 1. bad breakpoints on valid source lines are moved to the proper line of the expression 2. any bad breakpoints warn the user and halt execution upon entry to main so the user can see the live breakpoint state and have an opportunity to correct it. Thanks! -d _______________________________________________ Eap-bugs mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-bugs
