Debugging: Difference between revisions

From AMC-OS Developers
Jump to navigation Jump to search
(Initial creation)
 
mNo edit summary
 
Line 15: Line 15:
{| class="wikitable"
{| class="wikitable"
|+ Debugger functions
|+ Debugger functions
! scope="col" | Key
! scope="col" | Function
! scope="col" | Extensive description
|-
|-
| F1-F5 || Virtual screens ||
| F1-F5 || Virtual screens ||

Latest revision as of 22:39, 14 August 2012

Introduction

AMC-OS includes a debugger which can be called anytime. If kernel is compiled in DEBUG mode, the debugger will be automatically trigger if an exception occurs. The debugger is also called Faults Manager for this reason.

Entering debugger

As soon as main system is ready (ie. Faults Manager is loaded in memory and active), just hit ALT+F10 to switch to integrated debugger.

Before Faults Manager is ready, debug is done using AMC-OS DEBUG macros, and CLI/HLT combination...

Using faults manager

You may use the function keys to switch to the different debugging windows. Typically use the TAB, UP and DOWN keys in the different windows to navigate through the functions.

Debugger functions
Key Function Extensive description
F1-F5 Virtual screens
F6 Main debugging screen Display the exception that just occured, faultive application, and register contents
F7 CPU information Display extensive register contents, user and system stacks
F8 Physical memory dump

Display physical memory contents. You can navigate with different keys to up/down current address :

  • Plus/Minus : Next/previous screen
  • KeyUp/KeyDown : Up/down 0x10
  • Insert/Suppr : Up/down 0x100
  • Begin/End : Up/down 0x1000
  • PageUp/PageDown : Up/down 0x10000
  • I : Switch between paged and non-paged (using faultive application's CR3)
F9 Tasks Display applications, processes and threads information