Handler behaves like debugging despite breakpoint removed

[kresten]

A long handler in a substack continues, when called, to behave like debugging, although breakpoint is removed and app been closed, removed from memory and livecode (7.1.0) restarted. It is an old handler, which has been operating perfectly in older Livecode versions. Is this a known phenomenon ? Any suggestions how to escape from this trap ?

Kresten Bjerg, Copenhagen

[dunbarx]

Hi.

You run the handler, and it steps into the debugger? And there are no soft or hard breakpoints at all? Does it start at the same line each time?

Craig Newman

[kresten]

Yes it starts in the beginning each time.
I have run "Clear all breakpoints".
What is "soft breakpoints" ?

Kresten

[Klaus]

Hi Kresten,

a "soft breakpoint" is the red dot that appears when you click the line number in the script editor.
These are not as reliable as writing "breakpoint" (= a hard breakpoint) in the script.

Best

Klaus

[kresten]

Hi Klaus
Thank you for Info, but unfortunately no help for solving my stubborn problem.
Best regards

Kresten

[mwieder]

Look at the custom properties of the stack, especially the cREVGeneral propertyset.
If there are any entries in the breakpoints, breakpointconditions, and breakpointstates you will probably want to get rid of them.
Maybe the watches and watchstates as well.