Henry-Hiles/qmk_userspace
1
0
Fork 0
forked from mirrors/qmk_userspace
Code Pull requests Activity

Trim trailing whitespace

Browse source
This commit is contained in:
fauxpark 2017-12-09 16:56:58 +11:00 • committed by Jack Humbert
parent af37bb2f78
commit bb53635f33
28 changed files with 88 additions and 88 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/unit_testing.md
View file

@ -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