[Issue 12163] pdb debugging (win64): stepping loops points to incorrect lines

d-bugmail at puremagic.com d-bugmail at puremagic.com
Sat Feb 15 04:19:55 PST 2014


https://d.puremagic.com/issues/show_bug.cgi?id=12163



--- Comment #6 from Manu <turkeyman at gmail.com> 2014-02-15 04:19:53 PST ---
(In reply to comment #4)
> 13   }                          <-- missing/questionable

I should add, I don't think this is questionable at all.
All C compiler's I've ever used (many!) do this, and without it, it would be
impossible to place a breakpoint on the last line of the loop, which is a very
important tool. The reason you want to place a breakpoint on the closing '}' is
so you have a final opportunity to inspect the state of all variables within
that cycle of the loop.
If the last operation in the loop skipped right into the next cycle of the
loop, you would have nowhere you are able to break to inspect the result of
that operation.
It's obvious that DMD already does have a moment where it intends to step to
the 'end of the loop cycle', except rather than pointing to the '}', it
incorrectly points to the last significant line in the code, no matter how
deeply nested it happens to be.

-- 
Configure issuemail: https://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------


More information about the Digitalmars-d-bugs mailing list