Debug modes

Two debug modes exist and cohabit; one comes from the Virtual Jaguar legacy and has been fairly modified from the original, it can be activated via -a or --alpine. The second one is the new additional debugger activated via -D or --debugger.
The user has to decide what debug mode to use; the emulator UI will adapt following the mode.

Alpine mode

This mode has several features

1. Memory Browser
2. CPU Browser (M68K, GPU and DSP)
   This feature has a breakpoint allowance
3. OP Browser
4. M68K Listing Browser
5. RISC Listing Browser
6. Stack Browser
   This feature is available since the Rx version
7. HW registers browser
   This feature is available since the Rx version and display only the blitter

Debugger mode

This mode includes the Alpine mode features and additional ones; to get the most of this mode, the source code must be compiled / assembled with DWARF 2 debug information.

1. All Watch variables
2. Breakpoints for M68K functions
   Include delete and disable breakpoints
3. Breakpoint for exceptions
   Illegal instruction, address error, M68K Unimplemented instruction, and Exception not referenced exceptions
4. Call Stack
5. Exception Vector Table (M68K)
6. Heap Allocator
7. Locals variables
8. Memory windows (with an extended feature)
9. Restart of the code
10. Save memory dump
11. View of the current M68K, GPU and DSP code in separate tabs
    M68K assembly code tracing (step in and step over)
12. View of the source code files in a specific tab
    M68K & C source level tracing (step in and step over)
13. View cartridge directory and files
14. Output Video
15. M68K cycles usage displays in the emulator status window