about summary refs log tree commit diff stats
path: root/cpp/.traces/jump_unless_fallthrough
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2015-02-25 01:24:11 -0800
committerKartik K. Agaram <vc@akkartik.com>2015-02-25 01:24:11 -0800
commit6f5d7864f6c0c62b8849349cb182c61f8dbed452 (patch)
treec4c22032dc09eefbc3b55268044d29607804c4fd /cpp/.traces/jump_unless_fallthrough
parentdc3803320013059ad400853e3f6a2851f7f82c04 (diff)
downloadmu-6f5d7864f6c0c62b8849349cb182c61f8dbed452.tar.gz
832 - call-stack for C++ version
These #defines and references now span many different layers. Let's see
if the lack of encapsulation causes problems.

Also interesting to run into a case where I need to modify a
foundational layer and touch every single scenario/trace. Only
alternative was to duplicate all the different layers that add
instructions. Sign of problems with this model?
Diffstat (limited to 'cpp/.traces/jump_unless_fallthrough')
-rw-r--r--cpp/.traces/jump_unless_fallthrough4
1 files changed, 2 insertions, 2 deletions
diff --git a/cpp/.traces/jump_unless_fallthrough b/cpp/.traces/jump_unless_fallthrough
index 5d6a5d9e..c1981cd7 100644
--- a/cpp/.traces/jump_unless_fallthrough
+++ b/cpp/.traces/jump_unless_fallthrough
@@ -4,9 +4,9 @@ parse/0:   ingredient: {name: "1", type: 0}
 parse/0: instruction: 1
 parse/0:   ingredient: {name: "1", type: 0}
 parse/0:   product: {name: "123", type: 1}
-run/0: instruction 0
+run/0: instruction main/0
 run/0: ingredient 0 is 999
 run/0: jump-unless fell through
-run/0: instruction 1
+run/0: instruction main/1
 run/0: ingredient 0 is 1
 mem/0: storing in location 123