From 7b3b30a0f2f6476646eaf5facd405b73c952fc2b Mon Sep 17 00:00:00 2001 From: Peter Evans Date: Sun, 25 Feb 2018 16:14:05 -0600 Subject: [PATCH] Use addr2 for ws tests I take it back from the previous commit--the test was written with an assumption that was not how execute() works --- tests/vm_debug.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/tests/vm_debug.c b/tests/vm_debug.c index 8c25b61..b57463a 100644 --- a/tests/vm_debug.c +++ b/tests/vm_debug.c @@ -132,27 +132,27 @@ Test(vm_debug, cmd_writestate) args.addr1 = 111; args.target = "a"; vm_debug_cmd_writestate(&args); - cr_assert_eq(mach->cpu->A, args.addr1); + cr_assert_eq(mach->cpu->A, args.addr2); args.addr1 = 112; args.target = "x"; vm_debug_cmd_writestate(&args); - cr_assert_eq(mach->cpu->X, args.addr1); + cr_assert_eq(mach->cpu->X, args.addr2); args.addr1 = 113; args.target = "y"; vm_debug_cmd_writestate(&args); - cr_assert_eq(mach->cpu->Y, args.addr1); + cr_assert_eq(mach->cpu->Y, args.addr2); args.addr1 = 114; args.target = "p"; vm_debug_cmd_writestate(&args); - cr_assert_eq(mach->cpu->P, args.addr1); + cr_assert_eq(mach->cpu->P, args.addr2); args.addr1 = 115; args.target = "s"; vm_debug_cmd_writestate(&args); - cr_assert_eq(mach->cpu->S, args.addr1); + cr_assert_eq(mach->cpu->S, args.addr2); } Test(vm_debug, break)