Menu
▾
▴
[Valgrind-developers] [valgrind] Fix some spelling errors found by Lintian. Patch from Alessandro Ghedini <ghedo@debian.org>.
|
From: Julian S. <se...@so...> - 2020-01-23 09:54:29
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=9dcd3ab1f6709afb729c3b5f567f78e0b385c97f commit 9dcd3ab1f6709afb729c3b5f567f78e0b385c97f Author: Julian Seward <js...@ac...> Date: Thu Jan 23 10:53:36 2020 +0100 Fix some spelling errors found by Lintian. Patch from Alessandro Ghedini <gh...@de...>. Diff: --- VEX/priv/ir_defs.c | 2 +- callgrind/docs/cl-manual.xml | 6 +++--- coregrind/m_commandline.c | 2 +- coregrind/m_gdbserver/server.c | 2 +- coregrind/m_hashtable.c | 2 +- coregrind/m_scheduler/scheduler.c | 2 +- coregrind/m_xtree.c | 2 +- drd/docs/drd-manual.xml | 10 +++++----- gdbserver_tests/mchelp.stdoutB.exp | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-) diff --git a/VEX/priv/ir_defs.c b/VEX/priv/ir_defs.c index 7b6e847..176ca9b 100644 --- a/VEX/priv/ir_defs.c +++ b/VEX/priv/ir_defs.c @@ -5198,7 +5198,7 @@ void sanityCheckIRSB ( const IRSB* bb, const HChar* caller, if (bb->stmts_used < 0 || bb->stmts_size < 8 || bb->stmts_used > bb->stmts_size) /* this BB is so strange we can't even print it */ - vpanic("sanityCheckIRSB: stmts array limits wierd"); + vpanic("sanityCheckIRSB: stmts array limits weird"); /* Ensure each temp has a plausible type. */ for (i = 0; i < n_temps; i++) { diff --git a/callgrind/docs/cl-manual.xml b/callgrind/docs/cl-manual.xml index 31fcbaa..38dc73d 100644 --- a/callgrind/docs/cl-manual.xml +++ b/callgrind/docs/cl-manual.xml @@ -363,7 +363,7 @@ callgrind.out.<emphasis>pid</emphasis>.<emphasis>part</emphasis>-<emphasis>threa Afterwards, instrumentation can be controlled in two ways: first, interactively with: <screen>callgrind_control -i on</screen> (and switching off again by specifying "off" instead of "on"). Second, - instrumentation state can be programatically changed with the + instrumentation state can be programmatically changed with the macros <computeroutput><xref linkend="cr.start-instr"/>;</computeroutput> and <computeroutput><xref linkend="cr.stop-instr"/>;</computeroutput>. </para> @@ -371,7 +371,7 @@ callgrind.out.<emphasis>pid</emphasis>.<emphasis>part</emphasis>-<emphasis>threa <para>Similarly, the collection state at program start can be switched off by <option><xref linkend="opt.instr-atstart"/>=no</option>. During - execution, it can be controlled programatically with the + execution, it can be controlled programmatically with the macro <computeroutput>CALLGRIND_TOGGLE_COLLECT;</computeroutput>. Further, you can limit event collection to a specific function by using <option><xref linkend="opt.toggle-collect"/>=function</option>. @@ -723,7 +723,7 @@ Also see <xref linkend="cl-manual.limits"/>.</para> <para>Note that the resulting call graph will most probably not contain <function>main</function>, but will contain all the functions executed after instrumentation was enabled. - Instrumentation can also programatically enabled/disabled. See the + Instrumentation can also be programmatically enabled/disabled. See the Callgrind include file <computeroutput>callgrind.h</computeroutput> for the macro you have to use in your source code.</para> <para>For cache diff --git a/coregrind/m_commandline.c b/coregrind/m_commandline.c index e34d0f0..27c53ba 100644 --- a/coregrind/m_commandline.c +++ b/coregrind/m_commandline.c @@ -66,7 +66,7 @@ static HChar* read_dot_valgrindrc ( const HChar* dir ) if ( !sr_isError(fd) ) { Int res = VG_(fstat)( sr_Res(fd), &stat_buf ); /* Ignore if not owned by the current user, or is not a regular file, - or is world writeable (CVE-2008-4865). */ + or is world writable (CVE-2008-4865). */ if (res == 0 && stat_buf.uid == VG_(geteuid)() && VKI_S_ISREG(stat_buf.mode) diff --git a/coregrind/m_gdbserver/server.c b/coregrind/m_gdbserver/server.c index a2cb2b2..cc809a8 100644 --- a/coregrind/m_gdbserver/server.c +++ b/coregrind/m_gdbserver/server.c @@ -258,7 +258,7 @@ int handle_gdb_valgrind_command (char *mon, OutputSink *sink_wanted_at_return) " Valgrind internal host status/memory\n" " v.translate <addr> [<traceflags>] : debug translation of <addr> with <traceflags>\n" " (default traceflags 0b00100000 : show after instrumentation)\n" -" An additional flag 0b100000000 allows to show gdbserver instrumentation\n"); +" An additional flag 0b100000000 allows one to show gdbserver instrumentation\n"); } break; case 1: /* v.set */ diff --git a/coregrind/m_hashtable.c b/coregrind/m_hashtable.c index 4d53cf2..19c604d 100644 --- a/coregrind/m_hashtable.c +++ b/coregrind/m_hashtable.c @@ -296,7 +296,7 @@ void VG_(HT_print_stats) ( const VgHashTable *table, HT_Cmp_t cmp ) } VG_(message)(Vg_DebugMsg, - "nr occurences of" + "nr occurrences of" " chains of len N," " N-plicated keys," " N-plicated elts\n"); diff --git a/coregrind/m_scheduler/scheduler.c b/coregrind/m_scheduler/scheduler.c index a60bba8..77f78eb 100644 --- a/coregrind/m_scheduler/scheduler.c +++ b/coregrind/m_scheduler/scheduler.c @@ -2245,7 +2245,7 @@ void do_client_request ( ThreadId tid ) "to recompile such code, using the header files from this version of\n" "Valgrind, and not any previous version.\n" "\n" - "If you see this mesage in any other circumstances, it is probably\n" + "If you see this message in any other circumstances, it is probably\n" "a bug in Valgrind. In this case, please file a bug report at\n" "\n" " http://www.valgrind.org/support/bug_reports.html\n" diff --git a/coregrind/m_xtree.c b/coregrind/m_xtree.c index 078edc5..16635eb 100644 --- a/coregrind/m_xtree.c +++ b/coregrind/m_xtree.c @@ -977,7 +977,7 @@ void VG_(XT_massif_print) FP("n%u: %llu %s\n", n_groups, top_total, header->top_node_desc); /* Output depth 0 groups. */ - DMSG(1, "XT_massif_print outputing %u depth 0 groups\n", n_groups); + DMSG(1, "XT_massif_print outputting %u depth 0 groups\n", n_groups); for (i = 0; i < n_groups; i++) ms_output_group(fp, 0, 0, &groups[i], sig_sz, header->sig_threshold); diff --git a/drd/docs/drd-manual.xml b/drd/docs/drd-manual.xml index 7692dac..8e28e96 100644 --- a/drd/docs/drd-manual.xml +++ b/drd/docs/drd-manual.xml @@ -356,7 +356,7 @@ behavior of the DRD tool itself:</para> Data races that occur between a statement at the end of one thread and another thread can be missed if memory access information is discarded immediately after a thread has been joined. This option - allows to specify for how many joined threads memory access information + allows one to specify for how many joined threads memory access information should be retained. </para> </listitem> @@ -455,7 +455,7 @@ behavior of the DRD tool itself:</para> <para> Perform segment merging only after the specified number of new segments have been created. This is an advanced configuration option - that allows to choose whether to minimize DRD's memory usage by + that allows one to choose whether to minimize DRD's memory usage by choosing a low value or to let DRD run faster by choosing a slightly higher value. The optimal value for this parameter depends on the program being analyzed. The default value works well for most programs. @@ -1028,7 +1028,7 @@ available macros and client requests are: applications contain intentional races. There exist e.g. applications where the same value is assigned to a shared variable from two different threads. It may be more convenient to suppress such races than to solve - these. This client request allows to suppress such races. + these. This client request allows one to suppress such races. </para> </listitem> <listitem> @@ -1069,7 +1069,7 @@ available macros and client requests are: <listitem> <para> The client request <varname>VG_USERREQ__DRD_START_TRACE_ADDR</varname>, - which allows to trace all load and store activity for the specified + which allows one to trace all load and store activity for the specified address range. </para> </listitem> @@ -1393,7 +1393,7 @@ More information about Boost.Thread can be found here: OpenMP stands for <emphasis>Open Multi-Processing</emphasis>. The OpenMP standard consists of a set of compiler directives for C, C++ and Fortran programs that allows a compiler to transform a sequential program into a -parallel program. OpenMP is well suited for HPC applications and allows to +parallel program. OpenMP is well suited for HPC applications and allows one to work at a higher level compared to direct use of the POSIX threads API. While OpenMP ensures that the POSIX API is used correctly, OpenMP programs can still contain data races. So it definitely makes sense to verify OpenMP programs diff --git a/gdbserver_tests/mchelp.stdoutB.exp b/gdbserver_tests/mchelp.stdoutB.exp index d962e67..f8582de 100644 --- a/gdbserver_tests/mchelp.stdoutB.exp +++ b/gdbserver_tests/mchelp.stdoutB.exp @@ -87,7 +87,7 @@ debugging valgrind internals monitor commands: Valgrind internal host status/memory v.translate <addr> [<traceflags>] : debug translation of <addr> with <traceflags> (default traceflags 0b00100000 : show after instrumentation) - An additional flag 0b100000000 allows to show gdbserver instrumentation + An additional flag 0b100000000 allows one to show gdbserver instrumentation memcheck monitor commands: xb <addr> [<len>] prints validity bits for <len> (or 1) bytes at <addr> |
