From bb53635f33c213e5a940edea8b07026ef89aed42 Mon Sep 17 00:00:00 2001 From: fauxpark Date: Sat, 9 Dec 2017 16:56:58 +1100 Subject: Trim trailing whitespace --- docs/unit_testing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs/unit_testing.md') diff --git a/docs/unit_testing.md b/docs/unit_testing.md index 31aa79f82..06d23a9cc 100644 --- a/docs/unit_testing.md +++ b/docs/unit_testing.md @@ -52,7 +52,7 @@ In that model you would emulate the input, and expect a certain output from the Sometimes you might wonder why a variable gets changed and where, and this can be quite tricky to track down without having a debugger. It's of course possible to manually add print statements to track it, but you can also enable the variable trace feature. This works for both for variables that are changed by the code, and when the variable is changed by some memory corruption. -To take the feature into use add `VARIABLE_TRACE=x` to the end of you make command. `x` represents the number of variables you want to trace, which is usually 1. +To take the feature into use add `VARIABLE_TRACE=x` to the end of you make command. `x` represents the number of variables you want to trace, which is usually 1. Then at a suitable place in the code, call `ADD_TRACED_VARIABLE`, to begin the tracing. For example to trace all the layer changes, you can do this ```c -- cgit v1.2.3-24-g4f1b