← [Back to Twitter thread index](../README.md)

---
title: "no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-"
author: "NOTimothyLottes"
handle: "@NOTimothyLottes"
post_url: "https://x.com/NOTimothyLottes/status/2061123768429211767"
post_id: "2061123768429211767"
timestamp: "2026-05-31 16:32:54"
post_count: 5
reply_count: 2
repost_count: 0
like_count: 9
view_count: 2974
---

# @NOTimothyLottes — no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-

## Post 1 (2026-05-31 16:32:54)

no-debugger-debug / console / printf-style - prior evolved to one mmapped fixed-width-height log file with an atomic for multi-thread|process messages - but even that seems too complexy ...

## Post 2 (2026-05-31 16:35:58) — reply to Post 1

moving to this >>> CART file is mmapped on CPU with mapped GPU access (no file IO) - background page walker to ensure OS won't page it out - beginning of CART file is a grid of 32-bit unsigned values - hex dumping that as my 'log file' - either to term or GPU render

## Post 3 (2026-05-31 16:37:34) — reply to Post 2

hits the easy to debug CPU or GPU stuff in the same framework (simply write and it just appears) - it's always a HEX dump, but can show decimal by pretending it's a 4-bit/character terminal with a hex font :)

## Post 4 (2026-05-31 22:01:24) — reply to Post 1

@NOTimothyLottes Here I am still debugging by looking at if a single LED turns on.

## Post 5 (2026-06-01 01:05:59) — reply to Post 4

@retrotink2 That plus an oscilloscope … this is the way