about summary refs log tree commit diff stats
path: root/024jump.cc
diff options
context:
space:
mode:
authorKartik Agaram <vc@akkartik.com>2019-07-01 22:46:07 -0700
committerKartik Agaram <vc@akkartik.com>2019-07-01 23:09:58 -0700
commit120a740871dce0fbdc6d1dda09075540ebd8e683 (patch)
tree7a5d0d34d11a4185d56c7afd9efaffebe8dffd7d /024jump.cc
parent4d0a047f65eae8521d9ff936c7139db01a11f6f6 (diff)
downloadmu-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 '024jump.cc')
0 files changed, 0 insertions, 0 deletions
' href='#n111'>111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157