From: Julian Seward Date: Fri, 26 Jul 2002 11:34:39 +0000 (+0000) Subject: Wibbles for 1.0.0. X-Git-Tag: svn/VALGRIND_1_0_0~1 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=ecd4ee7a79fb7b27ab854888d6dc7f91187f156c;p=thirdparty%2Fvalgrind.git Wibbles for 1.0.0. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@540 --- diff --git a/cachegrind/docs/manual.html b/cachegrind/docs/manual.html index 28fceb752c..b715ee3dfe 100644 --- a/cachegrind/docs/manual.html +++ b/cachegrind/docs/manual.html @@ -19,17 +19,18 @@ a:active { color: #0000C0; text-decoration: none; } + Valgrind -

Valgrind, version 1.0

-This manual was majorly updated on 20020713 +

Valgrind, version 1.0.0

+This manual was last updated on 20020726

Valgrind is licensed under the GNU General Public License, @@ -129,12 +130,12 @@ modern Linux installations. Valgrind is licensed under the GNU General Public License, version 2. Read the file LICENSE in the source distribution for details. Some of the PThreads test cases, test/pth_*.c, are taken from -"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline -Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & +"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline +Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & Associates, Inc. - +

1.2 What it does with your program

Valgrind is designed to be as non-intrusive as possible. It works @@ -477,7 +478,7 @@ follows: increased using this parameter. The supplied value must be between 4 and 4096 inclusive, and must be a power of two.

--trace-children=no [the default]
+

--trace-children=no [the default]
--trace-children=yes

When enabled, Valgrind will trace into child processes. This is confusing and usually not what you want, so is disabled by @@ -743,7 +744,7 @@ shouldn't need to use them in the normal run of things. Nevertheless: - +

2.6 Explaination of error messages

Despite considerable sophistication under the hood, Valgrind can only @@ -880,7 +881,7 @@ has wrongly been deallocated with free: at 0x4004318C: __builtin_vec_new (vg_clientfuncs.c:152) by 0x4C21BC15: KLaola::readSBStream(int) const (klaola.cc:314) by 0x4C21C155: KLaola::stream(KLaola::OLENode const *) (klaola.cc:416) - by 0x4C21788F: OLEFilter::convert(QCString const &) (olefilter.cc:272) + by 0x4C21788F: OLEFilter::convert(QCString const &) (olefilter.cc:272) The following was told to me be the KDE 3 developers. I didn't know any of it myself. They also implemented the check itself. @@ -1648,7 +1649,7 @@ know. I don't promise to fix it, but I'd at least like to be aware of it. - +

3.5 Memory leak detection

Valgrind keeps track of all memory blocks issued in response to calls @@ -1796,27 +1797,25 @@ Programs which are known not to work are:

-Known platform-specific limitations: +Known platform-specific limitations, as of release 1.0.0:

(With valgrind versions 1.0pre4 and 1.0pre5) On Red Hat 7.3, - there have been reports of link errors (at program start time) - for threaded programs using __pthread_clock_gettime - and __pthread_clock_settime. This appears to be - due to /lib/librt-2.2.5.so needing them. - Unfortunately I do not understand enough about this problem to - fix it properly, and I can't reproduce it on my test RedHat 7.3 - system. Please mail me if you have more information / - understanding.

On Red Hat 7.3, there have been reports of link errors (at + program start time) for threaded programs using + __pthread_clock_gettime and + __pthread_clock_settime. This appears to be due to + /lib/librt-2.2.5.so needing them. Unfortunately I + do not understand enough about this problem to fix it properly, + and I can't reproduce it on my test RedHat 7.3 system. Please + mail me if you have more information / understanding.

- Things are likely to go badly wrong on Red Hat 7.3.92 ("Limbo" - public beta), especially with threaded programs. Don't expect - this to work. Basically valgrind won't work as-is with any - glibc-2.3 based system. Also it looks like Red Hat's 2.4.18 - kernel as hacked for Limbo gives problems, due to an extra entry - in the ELF frame constructed by the kernel. The 2.4.18 in the - standard Red Hat 7.3 release works fine, though.

Inlining of string functions with gcc-3.1 or above causes a @@ -2071,11 +2070,12 @@ The two steps are: specified manually, or manually on the command line, or "interesting" source files can be annotated automatically with the --auto=yes option. You can annotate C/C++ - files or assembly language files equally easily.

This step can be performed as many times as you like for each Step 2. You may want to do multiple annotations showing different information each time.

+ The steps are described in detail in the following sections.

@@ -2121,12 +2121,12 @@ all three levels (I1/D1/L2) of the cache from the command line using the Other noteworthy behaviour:

References that straddle two cache lines are treated as follows:
References that straddle two cache lines are treated as follows:
- If both blocks hit --> counted as one hit
- If one block hits, the other misses --> counted as one miss
- If both blocks miss --> counted as one miss (not two)
+

Instructions that modify a memory location (eg. inc and dec) are counted as doing just a read, ie. a single data @@ -2213,7 +2213,7 @@ Things to note about the cachegrind.out file: of around 15 MB.

- +

7.5 Cachegrind options

Cachegrind accepts all the options that Valgrind does, although some of them (ones related to memory checking) don't do anything when cache profiling.

@@ -2221,9 +2221,9 @@ Cachegrind accepts all the options that Valgrind does, although some of them The interesting cache-simulation specific options are:

--I1=<size>,<associativity>,<line_size>
- --D1=<size>,<associativity>,<line_size>
- --L2=<size>,<associativity>,<line_size>
+
--I1=<size>,<associativity>,<line_size>
+ --D1=<size>,<associativity>,<line_size>
+ --L2=<size>,<associativity>,<line_size>
[default: uses CPUID for automagic cache configuration]
Manually specifies the I1/D1/L2 cache configuration, where diff --git a/coregrind/docs/manual.html b/coregrind/docs/manual.html index 28fceb752c..b715ee3dfe 100644 --- a/coregrind/docs/manual.html +++ b/coregrind/docs/manual.html @@ -19,17 +19,18 @@ a:active { color: #0000C0; text-decoration: none; } + Valgrind -
Valgrind, version 1.0
-This manual was majorly updated on 20020713 +
Valgrind, version 1.0.0
+This manual was last updated on 20020726

-jseward@acm.org
+jseward@acm.org
Copyright © 2000-2002 Julian Seward
Valgrind is licensed under the GNU General Public License, @@ -129,12 +130,12 @@ modern Linux installations. Valgrind is licensed under the GNU General Public License, version 2. Read the file LICENSE in the source distribution for details. Some of the PThreads test cases, test/pth_*.c, are taken from -"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline -Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & +"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline +Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & Associates, Inc. - +
1.2 What it does with your program
Valgrind is designed to be as non-intrusive as possible. It works @@ -477,7 +478,7 @@ follows: increased using this parameter. The supplied value must be between 4 and 4096 inclusive, and must be a power of two.

--trace-children=no [the default]
+
--trace-children=no [the default]
--trace-children=yes
When enabled, Valgrind will trace into child processes. This is confusing and usually not what you want, so is disabled by @@ -743,7 +744,7 @@ shouldn't need to use them in the normal run of things. Nevertheless:

- +

2.6 Explaination of error messages

3.5 Memory leak detection

Valgrind keeps track of all memory blocks issued in response to calls @@ -1796,27 +1797,25 @@ Programs which are known not to work are:

-Known platform-specific limitations: +Known platform-specific limitations, as of release 1.0.0:

(With valgrind versions 1.0pre4 and 1.0pre5) On Red Hat 7.3, - there have been reports of link errors (at program start time) - for threaded programs using __pthread_clock_gettime - and __pthread_clock_settime. This appears to be - due to /lib/librt-2.2.5.so needing them. - Unfortunately I do not understand enough about this problem to - fix it properly, and I can't reproduce it on my test RedHat 7.3 - system. Please mail me if you have more information / - understanding.

On Red Hat 7.3, there have been reports of link errors (at + program start time) for threaded programs using + __pthread_clock_gettime and + __pthread_clock_settime. This appears to be due to + /lib/librt-2.2.5.so needing them. Unfortunately I + do not understand enough about this problem to fix it properly, + and I can't reproduce it on my test RedHat 7.3 system. Please + mail me if you have more information / understanding.

- Things are likely to go badly wrong on Red Hat 7.3.92 ("Limbo" - public beta), especially with threaded programs. Don't expect - this to work. Basically valgrind won't work as-is with any - glibc-2.3 based system. Also it looks like Red Hat's 2.4.18 - kernel as hacked for Limbo gives problems, due to an extra entry - in the ELF frame constructed by the kernel. The 2.4.18 in the - standard Red Hat 7.3 release works fine, though.

Inlining of string functions with gcc-3.1 or above causes a @@ -2071,11 +2070,12 @@ The two steps are: specified manually, or manually on the command line, or "interesting" source files can be annotated automatically with the --auto=yes option. You can annotate C/C++ - files or assembly language files equally easily.

This step can be performed as many times as you like for each Step 2. You may want to do multiple annotations showing different information each time.

+ The steps are described in detail in the following sections.

@@ -2121,12 +2121,12 @@ all three levels (I1/D1/L2) of the cache from the command line using the Other noteworthy behaviour:

References that straddle two cache lines are treated as follows:
References that straddle two cache lines are treated as follows:
- If both blocks hit --> counted as one hit
- If one block hits, the other misses --> counted as one miss
- If both blocks miss --> counted as one miss (not two)
+

Instructions that modify a memory location (eg. inc and dec) are counted as doing just a read, ie. a single data @@ -2213,7 +2213,7 @@ Things to note about the cachegrind.out file: of around 15 MB.

- +

7.5 Cachegrind options

Cachegrind accepts all the options that Valgrind does, although some of them (ones related to memory checking) don't do anything when cache profiling.

@@ -2221,9 +2221,9 @@ Cachegrind accepts all the options that Valgrind does, although some of them The interesting cache-simulation specific options are:

--I1=<size>,<associativity>,<line_size>
- --D1=<size>,<associativity>,<line_size>
- --L2=<size>,<associativity>,<line_size>
+
--I1=<size>,<associativity>,<line_size>
+ --D1=<size>,<associativity>,<line_size>
+ --L2=<size>,<associativity>,<line_size>
[default: uses CPUID for automagic cache configuration]
Manually specifies the I1/D1/L2 cache configuration, where diff --git a/docs/manual.html b/docs/manual.html index 28fceb752c..b715ee3dfe 100644 --- a/docs/manual.html +++ b/docs/manual.html @@ -19,17 +19,18 @@ a:active { color: #0000C0; text-decoration: none; } + Valgrind -
Valgrind, version 1.0
-This manual was majorly updated on 20020713 +
Valgrind, version 1.0.0
+This manual was last updated on 20020726

-jseward@acm.org
+jseward@acm.org
Copyright © 2000-2002 Julian Seward
Valgrind is licensed under the GNU General Public License, @@ -129,12 +130,12 @@ modern Linux installations. Valgrind is licensed under the GNU General Public License, version 2. Read the file LICENSE in the source distribution for details. Some of the PThreads test cases, test/pth_*.c, are taken from -"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline -Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & +"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline +Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & Associates, Inc. - +
1.2 What it does with your program
Valgrind is designed to be as non-intrusive as possible. It works @@ -477,7 +478,7 @@ follows: increased using this parameter. The supplied value must be between 4 and 4096 inclusive, and must be a power of two.

--trace-children=no [the default]
+
--trace-children=no [the default]
--trace-children=yes
When enabled, Valgrind will trace into child processes. This is confusing and usually not what you want, so is disabled by @@ -743,7 +744,7 @@ shouldn't need to use them in the normal run of things. Nevertheless:

- +

2.6 Explaination of error messages

3.5 Memory leak detection

Valgrind keeps track of all memory blocks issued in response to calls @@ -1796,27 +1797,25 @@ Programs which are known not to work are:

-Known platform-specific limitations: +Known platform-specific limitations, as of release 1.0.0:

(With valgrind versions 1.0pre4 and 1.0pre5) On Red Hat 7.3, - there have been reports of link errors (at program start time) - for threaded programs using __pthread_clock_gettime - and __pthread_clock_settime. This appears to be - due to /lib/librt-2.2.5.so needing them. - Unfortunately I do not understand enough about this problem to - fix it properly, and I can't reproduce it on my test RedHat 7.3 - system. Please mail me if you have more information / - understanding.

On Red Hat 7.3, there have been reports of link errors (at + program start time) for threaded programs using + __pthread_clock_gettime and + __pthread_clock_settime. This appears to be due to + /lib/librt-2.2.5.so needing them. Unfortunately I + do not understand enough about this problem to fix it properly, + and I can't reproduce it on my test RedHat 7.3 system. Please + mail me if you have more information / understanding.

- Things are likely to go badly wrong on Red Hat 7.3.92 ("Limbo" - public beta), especially with threaded programs. Don't expect - this to work. Basically valgrind won't work as-is with any - glibc-2.3 based system. Also it looks like Red Hat's 2.4.18 - kernel as hacked for Limbo gives problems, due to an extra entry - in the ELF frame constructed by the kernel. The 2.4.18 in the - standard Red Hat 7.3 release works fine, though.

Inlining of string functions with gcc-3.1 or above causes a @@ -2071,11 +2070,12 @@ The two steps are: specified manually, or manually on the command line, or "interesting" source files can be annotated automatically with the --auto=yes option. You can annotate C/C++ - files or assembly language files equally easily.

This step can be performed as many times as you like for each Step 2. You may want to do multiple annotations showing different information each time.

+ The steps are described in detail in the following sections.

@@ -2121,12 +2121,12 @@ all three levels (I1/D1/L2) of the cache from the command line using the Other noteworthy behaviour:

References that straddle two cache lines are treated as follows:
References that straddle two cache lines are treated as follows:
- If both blocks hit --> counted as one hit
- If one block hits, the other misses --> counted as one miss
- If both blocks miss --> counted as one miss (not two)
+

Instructions that modify a memory location (eg. inc and dec) are counted as doing just a read, ie. a single data @@ -2213,7 +2213,7 @@ Things to note about the cachegrind.out file: of around 15 MB.

- +

7.5 Cachegrind options

Cachegrind accepts all the options that Valgrind does, although some of them (ones related to memory checking) don't do anything when cache profiling.

@@ -2221,9 +2221,9 @@ Cachegrind accepts all the options that Valgrind does, although some of them The interesting cache-simulation specific options are:

--I1=<size>,<associativity>,<line_size>
- --D1=<size>,<associativity>,<line_size>
- --L2=<size>,<associativity>,<line_size>
+
--I1=<size>,<associativity>,<line_size>
+ --D1=<size>,<associativity>,<line_size>
+ --L2=<size>,<associativity>,<line_size>
[default: uses CPUID for automagic cache configuration]
Manually specifies the I1/D1/L2 cache configuration, where diff --git a/memcheck/docs/manual.html b/memcheck/docs/manual.html index 28fceb752c..b715ee3dfe 100644 --- a/memcheck/docs/manual.html +++ b/memcheck/docs/manual.html @@ -19,17 +19,18 @@ a:active { color: #0000C0; text-decoration: none; } + Valgrind -
Valgrind, version 1.0
-This manual was majorly updated on 20020713 +
Valgrind, version 1.0.0
+This manual was last updated on 20020726

-jseward@acm.org
+jseward@acm.org
Copyright © 2000-2002 Julian Seward
Valgrind is licensed under the GNU General Public License, @@ -129,12 +130,12 @@ modern Linux installations. Valgrind is licensed under the GNU General Public License, version 2. Read the file LICENSE in the source distribution for details. Some of the PThreads test cases, test/pth_*.c, are taken from -"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline -Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & +"Pthreads Programming" by Bradford Nichols, Dick Buttlar & Jacqueline +Proulx Farrell, ISBN 1-56592-115-1, published by O'Reilly & Associates, Inc. - +
1.2 What it does with your program
Valgrind is designed to be as non-intrusive as possible. It works @@ -477,7 +478,7 @@ follows: increased using this parameter. The supplied value must be between 4 and 4096 inclusive, and must be a power of two.

--trace-children=no [the default]
+
--trace-children=no [the default]
--trace-children=yes
When enabled, Valgrind will trace into child processes. This is confusing and usually not what you want, so is disabled by @@ -743,7 +744,7 @@ shouldn't need to use them in the normal run of things. Nevertheless:

- +

2.6 Explaination of error messages

3.5 Memory leak detection

Valgrind keeps track of all memory blocks issued in response to calls @@ -1796,27 +1797,25 @@ Programs which are known not to work are:

-Known platform-specific limitations: +Known platform-specific limitations, as of release 1.0.0:

(With valgrind versions 1.0pre4 and 1.0pre5) On Red Hat 7.3, - there have been reports of link errors (at program start time) - for threaded programs using __pthread_clock_gettime - and __pthread_clock_settime. This appears to be - due to /lib/librt-2.2.5.so needing them. - Unfortunately I do not understand enough about this problem to - fix it properly, and I can't reproduce it on my test RedHat 7.3 - system. Please mail me if you have more information / - understanding.

On Red Hat 7.3, there have been reports of link errors (at + program start time) for threaded programs using + __pthread_clock_gettime and + __pthread_clock_settime. This appears to be due to + /lib/librt-2.2.5.so needing them. Unfortunately I + do not understand enough about this problem to fix it properly, + and I can't reproduce it on my test RedHat 7.3 system. Please + mail me if you have more information / understanding.

- Things are likely to go badly wrong on Red Hat 7.3.92 ("Limbo" - public beta), especially with threaded programs. Don't expect - this to work. Basically valgrind won't work as-is with any - glibc-2.3 based system. Also it looks like Red Hat's 2.4.18 - kernel as hacked for Limbo gives problems, due to an extra entry - in the ELF frame constructed by the kernel. The 2.4.18 in the - standard Red Hat 7.3 release works fine, though.

Inlining of string functions with gcc-3.1 or above causes a @@ -2071,11 +2070,12 @@ The two steps are: specified manually, or manually on the command line, or "interesting" source files can be annotated automatically with the --auto=yes option. You can annotate C/C++ - files or assembly language files equally easily.

This step can be performed as many times as you like for each Step 2. You may want to do multiple annotations showing different information each time.

+ The steps are described in detail in the following sections.

@@ -2121,12 +2121,12 @@ all three levels (I1/D1/L2) of the cache from the command line using the Other noteworthy behaviour:

References that straddle two cache lines are treated as follows:
References that straddle two cache lines are treated as follows:
- If both blocks hit --> counted as one hit
- If one block hits, the other misses --> counted as one miss
- If both blocks miss --> counted as one miss (not two)
+

Instructions that modify a memory location (eg. inc and dec) are counted as doing just a read, ie. a single data @@ -2213,7 +2213,7 @@ Things to note about the cachegrind.out file: of around 15 MB.

- +

7.5 Cachegrind options

Cachegrind accepts all the options that Valgrind does, although some of them (ones related to memory checking) don't do anything when cache profiling.

@@ -2221,9 +2221,9 @@ Cachegrind accepts all the options that Valgrind does, although some of them The interesting cache-simulation specific options are:

--I1=<size>,<associativity>,<line_size>
- --D1=<size>,<associativity>,<line_size>
- --L2=<size>,<associativity>,<line_size>
+
--I1=<size>,<associativity>,<line_size>
+ --D1=<size>,<associativity>,<line_size>
+ --L2=<size>,<associativity>,<line_size>
[default: uses CPUID for automagic cache configuration]
Manually specifies the I1/D1/L2 cache configuration, where