use bochs magic breakpoints in the error printer

makes it easier to get a good state to do some investigating before reseting.
2024-10-13 20:53:13 -04:00
parent 4a013b4a59
commit c49de28a15
3 changed files with 30 additions and 20 deletions
--- a/include/util/bochs_magic.inc
+++ b/include/util/bochs_magic.inc
@@ -20,7 +20,8 @@

 %ifndef __INC_BOCHS_DEBUG_MAGIC

-;
+; for things like the error printer, opperate differently when we are targeting a dev (bochs) build
+%define __STEVIA_DEV_DEBUG
 ; port_e9_hack: enabled=1 needs to be set in bochsrc.txt/bxrc
 ;
 %ifnmacro __BOCHS_PRINTC
--- a/include/util/error_func.nasm
+++ b/include/util/error_func.nasm
@@ -22,7 +22,12 @@

 %macro ERROR 1
    mov al, %1           ; al = 1 byte error code mapped to ascii values
+    %ifdef __STEVIA_DEV_DEBUG
+    __BOCHS_MAGIC_DEBUG
+    %endif
    jmp error
+    
+    
 %endmacro

 ; pass error as ascii character in al, errors a-zA-Z or 0-9