Erel B4X founder Staff member Licensed User Longtime User May 22, 2018 #1 There is a confusing debugger issue in v5.00 related to one of the new optimizations. If you are calling a resumable sub from a different module then in many cases the optimized code will be used even if it shouldn't. Shouldn't means that there is a breakpoint in the resumable sub or the code was changed since you made a full compilation. This can cause changes to be ignored. The workaround is to clean the project (ctrl + p) if it happens. V5.01 with a fix to this issue will be released in the near future.
There is a confusing debugger issue in v5.00 related to one of the new optimizations. If you are calling a resumable sub from a different module then in many cases the optimized code will be used even if it shouldn't. Shouldn't means that there is a breakpoint in the resumable sub or the code was changed since you made a full compilation. This can cause changes to be ignored. The workaround is to clean the project (ctrl + p) if it happens. V5.01 with a fix to this issue will be released in the near future.
Erel B4X founder Staff member Licensed User Longtime User Aug 29, 2018 #3 There will be no v5.01. I eventually decided to not to release it as this bug is quite rare. The next version of B4i will include a large update to the debugger.
There will be no v5.01. I eventually decided to not to release it as this bug is quite rare. The next version of B4i will include a large update to the debugger.
