MagnitudeOS/littlefs
1
0
Fork 0
forked from Imagelibrary/littlefs
Code Pull Requests Activity

scripts: tracebd.py: Prioritize erases when rendering

Browse Source 
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.
This commit is contained in:
Christopher Haster
2025-04-19 10:17:04 -05:00
parent 9820e369a3
commit 2909da9c13
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
scripts/dbgtrace.py
View File

@@ -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 = (