From c442a5ad806b6cccbb3ec4c5744b14b0c1f31a01 Mon Sep 17 00:00:00 2001 From: Kartik Agaram Date: Mon, 25 Feb 2019 00:17:46 -0800 Subject: 4987 - support `browse_trace` tool in SubX I've extracted it into a separate binary, independent of my Mu prototype. I also cleaned up my tracing layer to be a little nicer. Major improvements: - Realized that incremental tracing really ought to be the default. And to minimize printing traces to screen. - Finally figured out how to combine layers and call stack frames in a single dimension of depth. The answer: optimize for the experience of `browse_trace`. Instructions occupy a range of depths based on their call stack frame, and minor details of an instruction lie one level deeper in each case. Other than that, I spent some time adjusting levels everywhere to make `browse_trace` useful. --- subx/drun | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'subx/drun') diff --git a/subx/drun b/subx/drun index 82584772..15c7f747 100755 --- a/subx/drun +++ b/subx/drun @@ -12,9 +12,9 @@ fi if [[ $1 == 'ex'* ]] then - CFLAGS=-g ./subx --map --trace run examples/$* 2>x + CFLAGS=-g ./subx --map --trace run examples/$* exit $? fi -CFLAGS=-g ./subx --map --trace run apps/$* 2>x +CFLAGS=-g ./subx --map --trace run apps/$* exit $? -- cgit 1.4.1-2-gfad0