1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
|
Description: Fix spelling-error-in-manpage found by lintian
Origin: vendor
Author: Alessandro Ghedini <ghedo@debian.org>
Reviewed-by: Alessandro Ghedini <ghedo@debian.org>
Last-Update: 2013-11-04
--- a/drd/docs/drd-manual.xml
+++ b/drd/docs/drd-manual.xml
@@ -356,7 +356,7 @@
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 @@
<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 @@
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 @@
<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 @@
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
--- a/docs/vgdb.1
+++ b/docs/vgdb.1
@@ -114,7 +114,7 @@
.PP
\fB\-\-port=<portnr>\fR
.RS 4
-Instructs vgdb to use tcp/ip and listen for GDB on the specified port nr rather than to use a pipe to communicate with GDB\&. Using tcp/ip allows to have GDB running on one computer and debugging a Valgrind process running on another target computer\&. Example:
+Instructs vgdb to use tcp/ip and listen for GDB on the specified port nr rather than to use a pipe to communicate with GDB\&. Using tcp/ip allows one to have GDB running on one computer and debugging a Valgrind process running on another target computer\&. Example:
.sp
.if n \{\
.RS 4
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -2037,7 +2037,7 @@
knowledge of the glibc stack cache implementation and by
examining the debug information of the pthread
library. This technique is thus somewhat fragile and might
- not work for all glibc versions. This has been succesfully
+ not work for all glibc versions. This has been successfully
tested with various glibc versions (e.g. 2.11, 2.16, 2.18)
on various platforms.</para>
</listitem>
|
