Ignore STOP-AFTER when stepping in the debugger

  • Thread starter Thread starter Simon L. Prinsloo
  • Start date Start date
Status
Not open for further replies.
S

Simon L. Prinsloo

Guest
If a STOP-AFTER phrase is in effect, the STOP condition is raised when the time-out is reached while stepping with the debugger. This leads to difficulty in identifying where the problem is. For starters, the code initially seems to "crash" mysteriously on illogical places in an inconsistent way while stepping. It can take some time before one realise that this erratic behaviour is caused by a STOP-AFTER high up in the stack. Once the programmer realise it is the STOP-AFTER, it becomes a race against the clock to reach the problem point. One that can often not be won. The only solution is to somehow disable the STOP-AFTER phrase. Bottom line, it is often easy to forget to restore the STOP-AFTER once debugging was completed. The suggestion is that the STOP-AFTER time out be ignored while stepping in the debugger.

Continue reading...
 
Status
Not open for further replies.
Back
Top