diff options
| author |  skullY <skullydazed@gmail.com> | 2020-02-27 20:53:50 -0800 |
|---|---|---|
| committer |  skullydazed <skullydazed@users.noreply.github.com> | 2020-03-05 16:00:10 -0800 |
| commit | 54c58ea6de61a0f1fefa06e8271e2e11f9027940 (patch) | |
| tree | 2ce4163cda8164edccd6f06f6e384861a205006c /docs/unit_testing.md | |
| parent | a95a314f78fd96aca7cc496b10bd310e28b1b66e (diff) | |
| download | qmk_firmware-54c58ea6de61a0f1fefa06e8271e2e11f9027940.tar.gz | |
Add explicit id tags to externally linked headers
Diffstat (limited to 'docs/unit_testing.md')
| -rw-r--r-- | docs/unit_testing.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/unit_testing.md b/docs/unit_testing.md index 06d23a9cc..4de5c217e 100644 --- a/docs/unit_testing.md +++ b/docs/unit_testing.md @@ -48,7 +48,7 @@ It's not yet possible to do a full integration test, where you would compile the In that model you would emulate the input, and expect a certain output from the emulated keyboard. -# Tracing Variables +# Tracing Variables :id=tracing-variables 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. |