Hi All,
    Has anyone else experienced some set Breakpoints not breaking the program run?
My pictured example shows the set Breakpoint being ignored with only the Stop statement halting my program run!?

(Click to enlarge)

This seems to have begun when I upgraded to v3.20, but I can't be certain of that, as some bp's do still work, whereas others don't,  50:50 approx
 
The previous Gambas version seemed to work with all breakpoints, and I used them constantly during debugging; but now
I have to use Stop statements all over the place, as Breakpoints can't be relied upon. Any ideas?

Thanks,
C.

 Maybe someone who has 3.20 running can check this.
I have no idea, running a lower version of Gambas

Does hitting the "Compile All" button fix anything?

 I have experienced the same thing, but intermittently.
I feel that there is something not being cleaned up when running from the IDE, so maybe Bruce is right.

Hi,
     By experimenting a little, I've found that sometimes a Breakpoint after a Stop statement does break the program run; but then Breakpoints subsequent to that don't.   However, pressing compileAll leads to none of my Breakpoints - placed before or after a Stop statement - working!  See picture

(Click to enlarge)

Will have to stick with Stops until this can be reproduced and fixed, I guess.

C.