For some debugging scenarios, the interesting operation is during kernel load, where the moment passes quickly and you don't have time to click and set a breakpoint in the UI.
For that workflow, it's:
Launch the emulator with the specified kernel
Set a breakpoint in the debugger (although it won't hit now, because it's too late)
Restart the kernel to run it again
Breakpoint hits
With this command line option, it's a lot easier:
Launch the emulator with the specified kernel and breakpoint option
Kernel launches and breakpoint hits
This can also benefit other scenarios where the user has to iterate frequently and run the program under debugger many times, and there's a time savings in not having to go through the UI each time.
This is geared toward execution breakpoints since that's the most common type of breakpoint.
For some debugging scenarios, the interesting operation is during kernel load, where the moment passes quickly and you don't have time to click and set a breakpoint in the UI.
For that workflow, it's:
With this command line option, it's a lot easier:
This can also benefit other scenarios where the user has to iterate frequently and run the program under debugger many times, and there's a time savings in not having to go through the UI each time.
This is geared toward execution breakpoints since that's the most common type of breakpoint.