zenithsiz/ftmemsim-valgrind
1
0
Fork 0
mirror of https://github.com/Zenithsiz/ftmemsim-valgrind.git synced 2026-02-11 22:08:14 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

spelling fixes

Browse Source 
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1715
This commit is contained in:
Dirk Mueller
2003-07-04 16:18:15 +00:00
parent 74079f47ac
commit faf02201e5
14 changed files with 20 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
memcheck/docs/mc_techdocs.html
View File

@@ -1327,7 +1327,7 @@ Improved code:
Once you understand the meaning of the instrumentation uinstrs,
discussed in detail above, the instrumentation scheme is fairly
straighforward. Each uinstr is instrumented in isolation, and the
straightforward. Each uinstr is instrumented in isolation, and the
instrumentation uinstrs are placed before the original uinstr.
Our running example continues below. I have placed a blank line
after every original ucode, to make it easier to see which
@@ -1346,7 +1346,7 @@ scheme, only checking where a failure of validity could cause the
original program to (seg)fault. So the use of values as memory
addresses causes a check, as do conditional jumps (these cause a check
on the definedness of the condition codes). And arguments
<code>PUSH</code>ed for helper calls are checked, hence the wierd
<code>PUSH</code>ed for helper calls are checked, hence the weird
restrictions on help call preambles described above.
<p>