v0.5.7: heap range on the boot screen — real-hardware geometry without a crash

The OptiPlex heap-corruption repro (guard report) came in hand-copied
and garbled; the exact heap start/end was the missing datum.  The heap
self-test range was serial-only; now it is also a boot marker, so the
next boot shows 'rsnix: heap 0x..-0x.. (N MiB) ok' on the framebuffer.

1 files changed, 6 insertions, 0 deletions

diff --git a/rsdos/src/main.rs b/rsdos/src/main.rs
index 60acc4e..cbbf2ba 100644
--- a/rsdos/src/main.rs
+++ b/rsdos/src/main.rs
@@ -245,6 +245,12 @@ pub unsafe extern "efiapi" fn efi_main(image_handle: Handle, system_table: *mut
 
     if rsnix::memory::self_test() {
         let hs = rsnix::memory::heap_stats();
+        rsnix::gop::boot_marker(&alloc::format!(
+            "rsnix: heap 0x{:x}-0x{:x} ({} MiB) ok",
+            hs.heap_start,
+            hs.heap_end,
+            hs.heap_size / 1024 / 1024
+        ));
         rsnix::serial_println!(
             "heap: self-test OK (0x{:x}..0x{:x} {} KiB free={} KiB)",
             hs.heap_start,