Debug Buggy?

C

CodeDancer

Member
Licensed User
Longtime User
I've noticed a few threads on debug problems but they don't appear to end with any definite conclusions. I am running B4A 2.22 and the problem is still here.
I have the one mentioned earlier this year. The first breakpoint is highlighted yellow and the IDE indicates a stop there, but the program has continued merrily on it's way. If the breakpoint is in a loop, it actually pauses on it the next time around.
If you put a bogus breakpoint in Activity_Create, the program will skip it (as it should) and breaks correctly on the first real breakpoint.
Any real fix in sight?
 
C

CodeDancer

Member
Licensed User
Longtime User
I upgraded to 2.3, but I'm sorry to say, the results are the same.
I can live with the work-around, but could you please point me to a starting point on figuring out what the logs are trying to tell me.
I spent almost 30 years getting a handle :) on Windows messages but this stuff (linux?) is new to me.
 
C

CodeDancer

Member
Licensed User
Longtime User
It happens on a slide show and a multiple video project. I tried another couple of projects and the debug appears to be O.K. on them.
I guess I will start to remove parts of the misbehaving projects to determine what causes debug to fail.

What log? The debug log for the device. I get so many errors and warnings on the unfiltered view, even when the application appears to be working fine, that I wondered if anyone had compiled a list of the ones that apply to B4A projects and what they all mean. What is important and what can be ignored.
 
F

fdx12345

Active Member
Licensed User
Longtime User
Breakpoint stoppage

For what it is worth:

I am having no problems. The program stops exactly at the breakpoint marker, even in the Activity create and other module files.
 
You must log in or register to reply here.
Top