From 2909da9c13be5c2323ac5fdcd5a501b69785e829 Mon Sep 17 00:00:00 2001 From: Christopher Haster Date: Sat, 19 Apr 2025 10:17:04 -0500 Subject: [PATCH] scripts: tracebd.py: Prioritize erases when rendering I've made this mistake before! One would think that it would be more interesting to show progs over erases when they overlap, since progs always subset erases and show more detail. However, erases occur much more rarely and are usually followed by progs, so when rendering is low resolution (ascii) it's easy for progs to completely cover up all erase operations. Prioritizing erases prevents this. At least this nuance is better documented this time around. --- scripts/dbgtrace.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/scripts/dbgtrace.py b/scripts/dbgtrace.py index 064529eb..0b78bdc2 100755 --- a/scripts/dbgtrace.py +++ b/scripts/dbgtrace.py @@ -49,9 +49,9 @@ WEAR_COLORS = ['1;30', '1;30', '1;30', '', '', '', '', '31', '31', '1;31'] # give more interesting operations a higher priority # -# note that while erase is more destructive than prog, all progs subset -# erases, so progs are more interesting -Z_ORDER = ['prog', 'erase', 'read', 'wear', 'noop'] +# note that while progs always subset erases, erases are much rarer, +# which is why we give them priority +Z_ORDER = ['erase', 'prog', 'read', 'wear', 'noop'] CHARS_DOTS = " .':" CHARS_BRAILLE = (