diff options
author | Kartik Agaram <vc@akkartik.com> | 2019-07-01 22:46:07 -0700 |
---|---|---|
committer | Kartik Agaram <vc@akkartik.com> | 2019-07-01 23:09:58 -0700 |
commit | 120a740871dce0fbdc6d1dda09075540ebd8e683 (patch) | |
tree | 7a5d0d34d11a4185d56c7afd9efaffebe8dffd7d /subx/apps/pack | |
parent | 4d0a047f65eae8521d9ff936c7139db01a11f6f6 (diff) | |
download | mu-120a740871dce0fbdc6d1dda09075540ebd8e683.tar.gz |
some primitives for emitting traces
Kinda hacky, but might scale enough for machine code. This was really hard to debug. Single tests passed, but when I ran all tests I got breakage because tests long before (from the 056trace layer) were not cleaning up properly. My instinct was to call clear-stream on Trace-stream, which was wrong (the trace didn't have the wrong contents, it was literally a bad object). It was also wrong in a counter-productive way: calling clear-stream on a real Trace stream (which is the size of a page of memory) takes a long time in emulated mode.
Diffstat (limited to 'subx/apps/pack')
-rwxr-xr-x | subx/apps/pack | bin | 43287 -> 43371 bytes |
1 files changed, 0 insertions, 0 deletions
diff --git a/subx/apps/pack b/subx/apps/pack
index 4f2ec6d4..a28f8b32 100755
--- a/subx/apps/pack
+++ b/subx/apps/pack
Binary files differ |