summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorErez Zukerman <bulk@ezuk.org>2017-02-02 18:32:21 -0500
committerErez Zukerman <bulk@ezuk.org>2017-02-02 18:32:21 -0500
commiteadb1afbd0dd13a38edad8948bf2d71766bc5760 (patch)
treeb072f89ee95dc56050f8d843c22bb8505ffce126
parent4344273c95cbf5552dc61f706b6a6fff18b93820 (diff)
fixes typo
-rw-r--r--Home.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Home.md b/Home.md
index 145b815eee..a2fe5ed2f7 100644
--- a/Home.md
+++ b/Home.md
@@ -1562,4 +1562,4 @@ This will add a traced variable named "layer" (the name is just for your informa
In order to actually detect changes to the variables you should call `VERIFY_TRACED_VARIABLES` around the code that you think that modifies the variable. If a variable is modified it will tell you between which two `VERIFY_TRACED_VARIABLES` calls the modification happened. You can then add more calls to track it down further. I don't recommend spamming the codebase with calls. It's better to start with a few, and then keep adding them in a binary search fashion. You can also delete the ones you don't need, as each call need to store the file name and line number in the ROM, so you can run out of memory if you add too many calls.
-Also remember to delete all the tracing code ones you have found the bug, as you wouldn't want to create a pull request with tracing code. \ No newline at end of file
+Also remember to delete all the tracing code once you have found the bug, as you wouldn't want to create a pull request with tracing code. \ No newline at end of file