From faf02201e55071d0a8143fbf33033c5866db088a Mon Sep 17 00:00:00 2001 From: Dirk Mueller Date: Fri, 4 Jul 2003 16:18:15 +0000 Subject: [PATCH] spelling fixes git-svn-id: svn://svn.valgrind.org/valgrind/trunk@1715 --- coregrind/demangle/cp-demangle.c | 8 ++++---- coregrind/demangle/cplus-dem.c | 4 ++-- coregrind/docs/coregrind_core.html | 4 ++-- coregrind/vg_include.h | 2 +- coregrind/vg_ldt.c | 2 +- coregrind/vg_main.c | 2 +- coregrind/vg_signals.c | 2 +- coregrind/vg_symtab2.c | 2 +- coregrind/vg_syscalls.c | 2 +- coregrind/vg_to_ucode.c | 2 +- helgrind/hg_main.c | 2 +- include/vg_skin.h | 2 +- memcheck/docs/mc_techdocs.html | 4 ++-- tests/unused/pth_threadpool.c | 2 +- 14 files changed, 20 insertions(+), 20 deletions(-) diff --git a/coregrind/demangle/cp-demangle.c b/coregrind/demangle/cp-demangle.c index 489cac158..355d467a8 100644 --- a/coregrind/demangle/cp-demangle.c +++ b/coregrind/demangle/cp-demangle.c @@ -78,7 +78,7 @@ #define NAMESPACE_SEPARATOR (dm->style == DMGL_JAVA ? "." : "::") /* If flag_verbose is zero, some simplifications will be made to the - output to make it easier to read and supress details that are + output to make it easier to read and suppress details that are generally not of interest to the average C++ programmer. Otherwise, the demangled representation will attempt to convey as much information as the mangled form. */ @@ -523,7 +523,7 @@ result_shift_caret (dm, position_offset) /* Returns non-zero if the character that comes right before the place where text will be added to the result is a space. In this case, - the caller should supress adding another space. */ + the caller should suppress adding another space. */ static int result_previous_char_is_space (dm) @@ -2459,7 +2459,7 @@ demangle_type (dm) RETURN_IF_ERROR (demangle_class_enum_type (dm, &encode_return_type)); /* If all that was just demangled is the two-character - special substitution token, supress the addition of a + special substitution token, suppress the addition of a new candidate for it. */ if (dm->next == next + 2) is_substitution_candidate = 0; @@ -3830,7 +3830,7 @@ VG_(java_demangle_v3) (mangled) end = next + len; demangled = NULL; - /* Replace occurances of JArray with TYPE[]. */ + /* Replace occurrences of JArray with TYPE[]. */ while (next < end) { char *open_str = VG_(strstr) (next, "JArray<"); diff --git a/coregrind/demangle/cplus-dem.c b/coregrind/demangle/cplus-dem.c index ed16d2419..3b9da8eb5 100644 --- a/coregrind/demangle/cplus-dem.c +++ b/coregrind/demangle/cplus-dem.c @@ -1111,7 +1111,7 @@ ada_demangle (mangled, option) /* This function performs most of what cplus_demangle use to do, but to be able to demangle a name with a B, K or n code, we need to have a longer term memory of what types have been seen. The original - now intializes and cleans up the squangle code info, while internal + now initializes and cleans up the squangle code info, while internal calls go directly to this routine to avoid resetting that info. */ static char * @@ -2624,7 +2624,7 @@ iterate_demangle_function (work, mangled, declp, scan) /* Iterate over occurrences of __, allowing names and types to have a "__" sequence in them. We must start with the first (not the last) occurrence, since "__" most often occur between independent mangled - parts, hence starting at the last occurence inside a signature + parts, hence starting at the last occurrence inside a signature might get us a "successful" demangling of the signature. */ while (scan[2]) diff --git a/coregrind/docs/coregrind_core.html b/coregrind/docs/coregrind_core.html index e1cbc06a2..d9cc53738 100644 --- a/coregrind/docs/coregrind_core.html +++ b/coregrind/docs/coregrind_core.html @@ -126,7 +126,7 @@ newer DWARF2 reader.

When you're ready to roll, just run your application as you would normally, but place valgrind --skin=the-selected-skin in -front of your usual command-line invokation. Note that you should run +front of your usual command-line invocation. Note that you should run the real (machine-code) executable here. If your application is started by, for example, a shell or perl script, you'll need to modify it to invoke Valgrind on the real executables. Running such scripts @@ -1193,7 +1193,7 @@ a kernel 2.2.X or 2.4.X system, subject to the following constraints:

  • Valgrind's signal simulation is not as robust as it could be. Basic POSIX-compliant sigaction and sigprocmask functionality is supplied, but it's conceivable that things could go badly awry - if you do wierd things with signals. Workaround: don't. + if you do weird things with signals. Workaround: don't. Programs that do non-POSIX signal tricks are in any case inherently unportable, so should be avoided if possible.

    • diff --git a/coregrind/vg_include.h b/coregrind/vg_include.h index f85819c27..ca5a1d9c5 100644 --- a/coregrind/vg_include.h +++ b/coregrind/vg_include.h @@ -234,7 +234,7 @@ extern ULong VG_(clo_stop_after); extern Int VG_(clo_dump_error); /* Number of parents of a backtrace. Default: 8. */ extern Int VG_(clo_backtrace_size); -/* Engage miscellaneous wierd hacks needed for some progs. */ +/* Engage miscellaneous weird hacks needed for some progs. */ extern Char* VG_(clo_weird_hacks); /* Should we run __libc_freeres at exit? Sometimes causes crashes. Default: YES. Note this is subservient to VG_(needs).libc_freeres; diff --git a/coregrind/vg_ldt.c b/coregrind/vg_ldt.c index 129a43257..0c3372f1d 100644 --- a/coregrind/vg_ldt.c +++ b/coregrind/vg_ldt.c @@ -162,7 +162,7 @@ Addr VG_(do_useseg) ( UInt seg_selector, Addr virtual_addr ) seg_selector &= 0x0000FFFF; /* Sanity check the segment selector. Ensure that TI=1 (LDT) and - that RPL=11b (least priviledge). These form the bottom 3 bits + that RPL=11b (least privilege). These form the bottom 3 bits of the selector. */ vg_assert((seg_selector & 7) == 7); diff --git a/coregrind/vg_main.c b/coregrind/vg_main.c index 8555bc2fe..746d68123 100644 --- a/coregrind/vg_main.c +++ b/coregrind/vg_main.c @@ -449,7 +449,7 @@ Bool VG_(logging_to_filedes) = True; vg_startup.S. We have to determine it early since we can't even correctly snapshot the startup machine state without it. */ /* Initially True. Safer to err on the side of SSEness and get SIGILL - than to not notice for some reason that we have SSE and get wierd + than to not notice for some reason that we have SSE and get weird errors later on. */ Bool VG_(have_ssestate) = True; diff --git a/coregrind/vg_signals.c b/coregrind/vg_signals.c index 0079a9481..3c9ba1ca9 100644 --- a/coregrind/vg_signals.c +++ b/coregrind/vg_signals.c @@ -1233,7 +1233,7 @@ Bool VG_(deliver_signals) ( void ) client really has a handler for this thread! */ vg_assert(vg_dcss.dcss_sigpending[sigNo]); - /* A recent addition, so as to stop seriously wierd progs dying + /* A recent addition, so as to stop seriously weird progs dying at the following assertion (which this renders redundant, btw). */ if (vg_scss.scss_per_sig[sigNo].scss_handler == VKI_SIG_IGN diff --git a/coregrind/vg_symtab2.c b/coregrind/vg_symtab2.c index 3de029331..19939510e 100644 --- a/coregrind/vg_symtab2.c +++ b/coregrind/vg_symtab2.c @@ -1138,7 +1138,7 @@ void read_debuginfo_dwarf2 ( SegInfo* si, UChar* dwarf2, Int dwarf2_sz ) understand this wrong, but I don't think so. I just had a look at the GDB DWARF2 reader... They - completly ignore "is_stmt" when recording line info ;-) + completely ignore "is_stmt" when recording line info ;-) That's the reason "objdump -S" works on files from the the intel fortran compiler. */ diff --git a/coregrind/vg_syscalls.c b/coregrind/vg_syscalls.c index b79ada6d2..291cddf9c 100644 --- a/coregrind/vg_syscalls.c +++ b/coregrind/vg_syscalls.c @@ -183,7 +183,7 @@ void mremap_segment ( Addr old_addr, UInt old_size, Addr new_addr, might return a large offset. Therefore we must not anymore test for < 0, but test for a real error by making sure the value in %eax is a real error number. Linus said he will make sure the no syscall - returns a value in -1 .. -4095 as a valid result so we can savely + returns a value in -1 .. -4095 as a valid result so we can safely test with -4095. END QUOTE diff --git a/coregrind/vg_to_ucode.c b/coregrind/vg_to_ucode.c index c2272ab75..cdf04b1e6 100644 --- a/coregrind/vg_to_ucode.c +++ b/coregrind/vg_to_ucode.c @@ -4559,7 +4559,7 @@ static Addr disInstr ( UCodeBlock* cb, Addr eip, Bool* isEnd ) if (dis) VG_(printf)("leave"); break; - /* ---------------- Misc wierd-ass insns --------------- */ + /* ---------------- Misc weird-ass insns --------------- */ case 0x27: /* DAA */ case 0x2F: /* DAS */ diff --git a/helgrind/hg_main.c b/helgrind/hg_main.c index f29b980a4..456378038 100644 --- a/helgrind/hg_main.c +++ b/helgrind/hg_main.c @@ -308,7 +308,7 @@ static inline EC_EIP getExeContext(Addr a) * segments are arranged to form an interference graph which indicates * whether two thread lifetime segments can possibly be concurrent. * If not, then memory with is exclusively accessed by one TLS can be - * passed on to another TLS without an error occuring, and without + * passed on to another TLS without an error occurring, and without * moving it from Excl state. * * At present this only considers thread creation and join as diff --git a/include/vg_skin.h b/include/vg_skin.h index 86632e7f4..cc5cfe572 100644 --- a/include/vg_skin.h +++ b/include/vg_skin.h @@ -512,7 +512,7 @@ typedef enum { NOP, /* Null op */ - LOCK, /* Indicate the existance of a LOCK prefix (functionally NOP) */ + LOCK, /* Indicate the existence of a LOCK prefix (functionally NOP) */ /* Moving values around */ GET, PUT, /* simulated register <--> TempReg */ diff --git a/memcheck/docs/mc_techdocs.html b/memcheck/docs/mc_techdocs.html index 50899ea93..29ff9aebc 100644 --- a/memcheck/docs/mc_techdocs.html +++ b/memcheck/docs/mc_techdocs.html @@ -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 -PUSHed for helper calls are checked, hence the wierd +PUSHed for helper calls are checked, hence the weird restrictions on help call preambles described above.

    diff --git a/tests/unused/pth_threadpool.c b/tests/unused/pth_threadpool.c index 30f15955e..2da195019 100644 --- a/tests/unused/pth_threadpool.c +++ b/tests/unused/pth_threadpool.c @@ -293,7 +293,7 @@ void *tpool_thread(void *arg) else tpool->queue_head = my_workp->next; - printf("worker %d: dequeing item %d\n", pthread_self(), my_workp->next); + printf("worker %d: dequeuing item %d\n", pthread_self(), my_workp->next); /* Handle waiting add_work threads */ if ((!tpool->do_not_block_when_full) &&