Android Tutorial Rapid Debugger

Basic4android v3.0 includes a new debugger named rapid debugger.

The rapid debugger is a very sophisticated debugger with features not available in any other native Android development tool.

The rapid debugger is an important addition to Basic4android. It will increase your productivity as it makes the "write code -> test result" cycle much quicker.

Using this deployment mode is similar to using the standard debugger ("legacy" debugger).


Rapid Debugger advantages

• Very quick compilation and installation. Usually in less than one or two seconds.
  
• In most cases (after the first installation) there is no need to reinstall the APK. This means that the deployment is much quicker. With B4A-Bridge there is no need to approve the installation.
• Hot code swapping (edit and continue). You can modify the code while the app runs, hit Save and the code will be updated.
• Powerful variables browser:
  
  
  

• Watch Expressions (v3.50):
  
  
  
  
  Allows you to evaluate expressions during breakpoints.

Limitations

• The runtime execution in this mode is slower. In some cases it is slightly slower and in others it can be significantly slower. The rapid debugger is not suitable for debugging "real-time" games or CPU intensive tasks. This is why the legacy debugger is kept.
  Starting from v3.50 the runtime performance of the rapid debugger is close to Release mode.
  
• Hot code swapping is very powerful. You can even add subs or modify existing subs. However you cannot add or remove global variables.
• Unlike the legacy debugger, the app cannot run when the IDE is not connected. It will wait for 10 seconds for the IDE to connect and then exit.

 

[Jack Cole]

What is the expected behavior of the rapid debugger when a programming error is encountered when running an app (such as a null pointer exception)? It has always just crashed out of the app and exited rather than pausing as the legacy debugger does. It does not take me to the line number where the error is. I have tried this in multiple apps and on multiple machines with the same results.

 

[Erel]

It should print the full error message in the logs.
If the exception is not inside a Try / Catch block then it should exit the app immediately.

It should also take you to the correct location. There are however some issues with the reported line numbers.

 

[Jack Cole]

Thank you Erel. That makes sense.

 

[kiki78]

I can't use Rapid Debugger with B4A 4.30

Legacy Debug and Release works fine, but when I try Rapid Debug, I receive message box with :

An error occurred.
Rapid Debugger failed to connect to device. Please try to run again.

Compilation and installation is ok, but this message appear just after.

I try with USB and B4A-Bridge and the result is the same.

I try to downgrade to 4.00 and Rapid work fine, then reinstall 4.30 and Rapid don't work.

Any idea ?

Regards

 

[Erel]

Yes. You need to use Java 7+ (set under Tools - Configure Paths).

 

[kiki78]

Thank you Erel, this is exactly that

 

[Dave O]

If I'm running the rapid debugger and I make a change in the Designer (and save the change), it doesn't seem to take effect until I quit and restart the debugging session.

Is there a way to make UI changes in the Designer while the RD is running?

 

[klaus]

You can click on this button

, this will restart the program.