You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(32) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
(32) |
2
(22) |
3
(47) |
4
(29) |
5
(18) |
6
(16) |
|
7
(21) |
8
(29) |
9
(23) |
10
(68) |
11
(20) |
12
(17) |
13
(17) |
|
14
(27) |
15
(26) |
16
(21) |
17
(13) |
18
(19) |
19
(29) |
20
(13) |
|
21
(9) |
22
(8) |
23
(29) |
24
(56) |
25
(21) |
26
(46) |
27
(33) |
|
28
(25) |
29
(41) |
30
(35) |
31
(28) |
|
|
|
|
From: <sv...@va...> - 2005-08-03 22:59:42
|
Author: de Date: 2005-08-03 23:59:40 +0100 (Wed, 03 Aug 2005) New Revision: 164 Log: forgot some more ... Removed: trunk/docs/FAQ/images/ |
|
From: <sv...@va...> - 2005-08-03 22:59:07
|
Author: de
Date: 2005-08-03 23:59:06 +0100 (Wed, 03 Aug 2005)
New Revision: 163
Log:
forgot to delete one ...
Removed:
trunk/docs/FAQ/vg_basic.css
Deleted: trunk/docs/FAQ/vg_basic.css
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/vg_basic.css 2005-08-03 22:58:20 UTC (rev 162)
+++ trunk/docs/FAQ/vg_basic.css 2005-08-03 22:59:06 UTC (rev 163)
@@ -1,62 +0,0 @@
-/* default link colours */
-a, a:link, a:visited, a:active { color: #74240f; }
-a:hover { color: #888800; }
-
-body {=20
- color: #202020;=20
- background-color: #ffffff;
-}
-
-body, td {
- font-size: 90%;
- line-height: 125%;
- font-family: Arial, Geneva, Helvetica, sans-serif;
-}
-
-h1, h2, h3, h4 { color: #74240f; }
-h3 { margin-bottom: 0.4em; }
-
-code, tt, pre { color: #3366cc; }
-code, tt { color: #761596; }
-
-pre.programlisting {
- color: #000000;
- padding: 0.5em;
- background: #f2f2f9;
- border: 1px solid #3366cc;
-}
-pre.screen {
- color: #000000;
- padding: 0.5em;
- background: #eeeeee;
- border: 1px solid #626262;
-}
-
-ul { list-style: url("images/li-brown.png"); }
-
-.titlepage hr {
- height: 1px;
- border: 0px;
- background-color: #7f7f7f;
-}
-
-/* header / footer nav tables */
-table.nav {
- color: #0f7355;
- border: solid 1px #0f7355;
- background: #edf7f4;
- background-color: #edf7f4;
- margin-bottom: 0.5em;
-}
-/* don't have underlined links in chunked nav menus */
-table.nav a { text-decoration: none; }
-table.nav a:hover { text-decoration: underline; }
-table.nav td { font-size: 85%; }
-
-/* yellow box just for massif blockquotes */
-blockquote {
- padding: 0.5em;
- background: #fffbc9;=20
- border: solid 1px #ffde84;=20
-}
-
|
|
From: <sv...@va...> - 2005-08-03 22:58:23
|
Author: de Date: 2005-08-03 23:58:20 +0100 (Wed, 03 Aug 2005) New Revision: 162 Log: deleted old faq files Removed: trunk/docs/FAQ/valgrind-FAQ.html.tar.bz2 trunk/docs/FAQ/valgrind-FAQ.pdf.bz2 trunk/docs/FAQ/valgrind-FAQ.ps.bz2 Deleted: trunk/docs/FAQ/valgrind-FAQ.html.tar.bz2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (Binary files differ) Deleted: trunk/docs/FAQ/valgrind-FAQ.pdf.bz2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (Binary files differ) Deleted: trunk/docs/FAQ/valgrind-FAQ.ps.bz2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (Binary files differ) |
|
From: <sv...@va...> - 2005-08-03 22:57:07
|
Author: de
Date: 2005-08-03 23:57:01 +0100 (Wed, 03 Aug 2005)
New Revision: 161
Log:
one-page faq coming up, as requested :)
Removed:
trunk/docs/FAQ/faq.abort.html
trunk/docs/FAQ/faq.background.html
trunk/docs/FAQ/faq.help.html
trunk/docs/FAQ/faq.installing.html
trunk/docs/FAQ/faq.misc.html
trunk/docs/FAQ/faq.notfound.html
trunk/docs/FAQ/faq.unexpected.html
trunk/docs/FAQ/license.gfdl.html
Modified:
trunk/docs/FAQ/index.html
Deleted: trunk/docs/FAQ/faq.abort.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.abort.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/faq.abort.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,214 +0,0 @@
-<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"faq.installing.html"><img src=3D"images/prev.png" width=3D"18" h=
eight=3D"21" border=3D"0" alt=3D"Prev"></a></td>
-<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
-<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
-<th align=3D"center" valign=3D"middle">Valgrind FAQ</th>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"faq.unexpected.html"><img src=3D"images/next.png" width=3D"18" h=
eight=3D"21" border=3D"0" alt=3D"Next"></a></td>
-</tr></table></div>
-<div class=3D"sect1" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.abort"></a>4.=A0Valgrind aborts unexpectedly</h2></div></=
div>
-<div></div>
-</div>
-<div class=3D"qandaset">
-<dl>
-<dt>4.1. <a href=3D"faq.abort.html#faq.exit_errors">Programs run OK on V=
algrind, but at exit produce a bunch
- of errors a bit like this:</a>
-</dt>
-<dt>4.2. <a href=3D"faq.abort.html#faq.bugdeath">My (buggy) program dies=
like this:</a>
-</dt>
-<dt>4.3. <a href=3D"faq.abort.html#faq.msgdeath">My program dies, printi=
ng a message like this along the
- way:</a>
-</dt>
-<dt>4.4. <a href=3D"faq.abort.html#faq.defdeath">My program dies like th=
is:</a>
-</dt>
-</dl>
-<table border=3D"0" summary=3D"Q and A Set">
-<col align=3D"left" width=3D"1%">
-<tbody>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.exit_errors"></a><a name=3D"id2459844"></a><b>4.1.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>Programs run OK on Valgrind, but at=
exit produce a bunch
- of errors a bit like this:</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>
-</p>
-<pre class=3D"programlisting">
-=3D=3D20755=3D=3D Invalid read of size 4
-=3D=3D20755=3D=3D at 0x40281C8A: _nl_unload_locale (loadlocale.c:238)
-=3D=3D20755=3D=3D by 0x4028179D: free_mem (findlocale.c:257)
-=3D=3D20755=3D=3D by 0x402E0962: __libc_freeres (set-freeres.c:34)
-=3D=3D20755=3D=3D by 0x40048DCC: vgPlain___libc_freeres_wrapper (vg_c=
lientfuncs.c:585)
-=3D=3D20755=3D=3D Address 0x40CC304C is 8 bytes inside a block of siz=
e 380 free'd
-=3D=3D20755=3D=3D at 0x400484C9: free (vg_clientfuncs.c:180)
-=3D=3D20755=3D=3D by 0x40281CBA: _nl_unload_locale (loadlocale.c:246)
-=3D=3D20755=3D=3D by 0x40281218: free_mem (setlocale.c:461)
-=3D=3D20755=3D=3D by 0x402E0962: __libc_freeres (set-freeres.c:34)
-</pre>
-<p>
-
- and then die with a segmentation fault.</p>
-<p>When the program exits, Valgrind runs the procedure
- <tt class=3D"literal">__libc_freeres()</tt> in glibc. This is a hook
- for memory debuggers, so they can ask glibc to free up any
- memory it has used. Doing that is needed to ensure that
- Valgrind doesn't incorrectly report space leaks in glibc.</p>
-<p>Problem is that running
- <tt class=3D"literal">__libc_freeres()</tt> in older glibc versions
- causes this crash.</p>
-<p>WORKAROUND FOR 1.1.X and later
- versions of Valgrind: use the
- <tt class=3D"literal">--run-libc-freeres=3Dno</tt> flag. You may then =
get
- space leak reports for glibc-allocations (please _don't_ report
- these to the glibc people, since they are not real leaks), but
- at least the program runs.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.bugdeath"></a><a name=3D"id2459918"></a><b>4.2.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>My (buggy) program dies like this:<=
/p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<pre class=3D"screen">
-% valgrind: vg_malloc2.c:442 (bszW_to_pszW): Assertion 'pszW >=3D 0' =
failed.
-</pre>
-<p>If Memcheck (the memory checker) shows any invalid reads,
- invalid writes and invalid frees in your program, the above may
- happen. Reason is that your program may trash Valgrind's
- low-level memory manager, which then dies with the above
- assertion, or something like this. The cure is to fix your
- program so that it doesn't do any illegal memory accesses. The
- above failure will hopefully go away after that.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.msgdeath"></a><a name=3D"id2458703"></a><b>4.3.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>My program dies, printing a message=
like this along the
- way:</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<pre class=3D"screen">
-% disInstr: unhandled instruction bytes: 0x66 0xF 0x2E 0x5
-</pre>
-<p>Older versions did not support some x86 instructions,
- particularly SSE/SSE2 instructions. Try a newer Valgrind; we
- now support almost all instructions. If it still happens with
- newer versions, if the failing instruction is an SSE/SSE2
- instruction, you might be able to recompile your program
- without it by using the flag
- <tt class=3D"computeroutput">-march</tt> to gcc. Either way,
- let us know and we'll try to fix it.</p>
-<p>Another possibility is that your program has a bug and
- erroneously jumps to a non-code address, in which case you'll
- get a SIGILL signal. Memcheck/Addrcheck may issue a warning
- just before this happens, but they might not if the jump
- happens to land in addressable memory.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.defdeath"></a><a name=3D"id2458751"></a><b>4.4.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>My program dies like this:</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<pre class=3D"screen">
-% error: /lib/librt.so.1: symbol __pthread_clock_settime,=20
- version GLIBC_PRIVATE not defined in file libpthread.so.0 with link ti=
me reference
-</pre>
-<p>This is a total swamp. Nevertheless there is a way out.
- It's a problem which is not easy to fix. Really the problem is
- that <tt class=3D"filename">/lib/librt.so.1</tt> refers to some
- symbols <tt class=3D"literal">__pthread_clock_settime</tt> and
- <tt class=3D"literal">__pthread_clock_gettime</tt> in
- <tt class=3D"filename">/lib/libpthread.so</tt> which are not intended
- to be exported, ie they are private.</p>
-<p>Best solution is to ensure your program does not use
- <tt class=3D"filename">/lib/librt.so.1</tt>.</p>
-<p>However ... since you're probably not using it directly,
- or even knowingly, that's hard to do. You might instead be
- able to fix it by playing around with
- <tt class=3D"filename">coregrind/vg_libpthread.vs</tt>. Things to
- try:</p>
-<p>Remove this:</p>
-<pre class=3D"programlisting">
-GLIBC_PRIVATE {
- __pthread_clock_gettime;
- __pthread_clock_settime;
-};
-</pre>
-<p>or maybe remove this</p>
-<pre class=3D"programlisting">
-GLIBC_2.2.3 {
- __pthread_clock_gettime;
- __pthread_clock_settime;
-} GLIBC_2.2;
-</pre>
-<p>or maybe add this:</p>
-<pre class=3D"programlisting">
-GLIBC_2.2.4 {
- __pthread_clock_gettime;
- __pthread_clock_settime;
-} GLIBC_2.2;
-
-GLIBC_2.2.5 {
- __pthread_clock_gettime;
- __pthread_clock_settime;
-} GLIBC_2.2;
-</pre>
-<p>or some combination of the above. After each change you
- need to delete <tt class=3D"filename">coregrind/libpthread.so</tt> and
- do <tt class=3D"computeroutput">make && make
- install</tt>.</p>
-<p>I just don't know if any of the above will work. If you
- can find a solution which works, I would be interested to hear
- it.</p>
-<p>To which someone replied:</p>
-<pre class=3D"screen">
-I deleted this:
-
-GLIBC_2.2.3 {=20
- __pthread_clock_gettime;=20
- __pthread_clock_settime;=20
-} GLIBC_2.2;=20
-
-and it worked.
-</pre>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
-<tr>
-<td rowspan=3D"2" width=3D"40%" align=3D"left">
-<a accesskey=3D"p" href=3D"faq.installing.html"><<=A03.=A0Compilin=
g, installing and configuring</a>=A0</td>
-<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
-<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"faq.unexpected.html">5.=A0Valgrind behaves unexpectedly=A0>><=
/a>
-</td>
-</tr>
-<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
-</table>
-</div>
Deleted: trunk/docs/FAQ/faq.background.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.background.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/faq.background.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,84 +0,0 @@
-<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"index.html"><img src=3D"images/prev.png" width=3D"18" height=3D"=
21" border=3D"0" alt=3D"Prev"></a></td>
-<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
-<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
-<th align=3D"center" valign=3D"middle">Valgrind FAQ</th>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"faq.installing.html"><img src=3D"images/next.png" width=3D"18" h=
eight=3D"21" border=3D"0" alt=3D"Next"></a></td>
-</tr></table></div>
-<div class=3D"sect1" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.background"></a>2.=A0Background</h2></div></div>
-<div></div>
-</div>
-<div class=3D"qandaset">
-<dl>
-<dt>2.1. <a href=3D"faq.background.html#faq.pronounce">How do you pronou=
nce "Valgrind"?</a>
-</dt>
-<dt>2.2. <a href=3D"faq.background.html#faq.whence">Where does the name =
"Valgrind" come from?</a>
-</dt>
-</dl>
-<table border=3D"0" summary=3D"Q and A Set">
-<col align=3D"left" width=3D"1%">
-<tbody>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.pronounce"></a><a name=3D"id2507613"></a><b>2.1.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>How do you pronounce "Valgrind"?</p=
></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>The "Val" as in the world "value". The "grind" is
- pronounced with a short 'i' -- ie. "grinned" (rhymes with
- "tinned") rather than "grined" (rhymes with "find").</p>
-<p>Don't feel bad: almost everyone gets it wrong at
- first.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.whence"></a><a name=3D"id2507641"></a><b>2.2.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>Where does the name "Valgrind" come=
from?</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>From Nordic mythology. Originally (before release) the
- project was named Heimdall, after the watchman of the Nordic
- gods. He could "see a hundred miles by day or night, hear the
- grass growing, see the wool growing on a sheep's back" (etc).
- This would have been a great name, but it was already taken by
- a security package "Heimdal".</p>
-<p>Keeping with the
- Nordic theme, Valgrind was chosen. Valgrind is the name of the
- main entrance to Valhalla (the Hall of the Chosen Slain in
- Asgard). Over this entrance there resides a wolf and over it
- there is the head of a boar and on it perches a huge eagle,
- whose eyes can see to the far regions of the nine worlds. Only
- those judged worthy by the guardians are allowed to pass
- through Valgrind. All others are refused entrance.</p>
-<p>It's not short for "value grinder", although that's not a
- bad guess.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
-<tr>
-<td rowspan=3D"2" width=3D"40%" align=3D"left">
-<a accesskey=3D"p" href=3D"index.html"><<=A0Valgrind FAQ</a>=A0</t=
d>
-<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
-<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"faq.installing.html">3.=A0Compiling, installing and configuring=A0&=
gt;></a>
-</td>
-</tr>
-<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
-</table>
-</div>
Deleted: trunk/docs/FAQ/faq.help.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.help.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/faq.help.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,92 +0,0 @@
-<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"faq.misc.html"><img src=3D"images/prev.png" width=3D"18" height=3D=
"21" border=3D"0" alt=3D"Prev"></a></td>
-<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
-<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
-<th align=3D"center" valign=3D"middle">Valgrind FAQ</th>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"license.gfdl.html"><img src=3D"images/next.png" width=3D"18" hei=
ght=3D"21" border=3D"0" alt=3D"Next"></a></td>
-</tr></table></div>
-<div class=3D"sect1" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.help"></a>8.=A0How To Get Further Assistance</h2></div></=
div>
-<div></div>
-</div>
-<div class=3D"sect2" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h3 class=3D"title">
-<a name=3D"faq.unanswered"></a>8.1.=A0If Your Question Still Isn't Answe=
red ...</h3></div></div>
-<div></div>
-</div>
-<p>Please read all of this section before posting. It's a bit
-long, but you may be about to make a fool of yourself in front of
-50,000 people and waste hundreds of hours of their time. Don't
-you think it's worth spending some of your time to read and
-follow these instructions?</p>
-<p>If you think an answer is incomplete or inaccurate, please
-e-mail <a href=3D"mailto:val...@va..." target=3D"_top">valgrind=
@valgrind.org</a>.</p>
-<p>Read the appropriate section(s) of the Manual(s):=20
-<a href=3D"http://www.valgrind.org/docs/" target=3D"_top">Valgrind=20
-Documentation</a>.</p>
-<p>Read the Valgrind Distribution Documents.</p>
-<p><a href=3D"http://search.gmane.org" target=3D"_top">Search</a> the=20
-<a href=3D"http://news.gmane.org/gmane.comp.debugging.valgrind" target=3D=
"_top">valgrind-users</a> mailing list archives, using the group name=20
-<tt class=3D"computeroutput">gmane.comp.debugging.valgrind</tt>.</p>
-<p>Only when you have tried all of these things and are still
-stuck, should you post to the <a href=3D"http://lists.sourceforge.net/li=
sts/listinfo/valgrind-users" target=3D"_top">valgrind-users mailing list<=
/a>. Make sure you read the next section first: <a href=3D"faq.help.html#=
faq.request">What to Put in a Request for Help</a>.</p>
-</div>
-<div class=3D"sect2" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h3 class=3D"title">
-<a name=3D"faq.request"></a>8.2.=A0What to Put in a Request for Help</h3=
></div></div>
-<div></div>
-</div>
-<p>Please read the following advice carefully about how to
-write your posting or email. Making a complete posting will
-greatly increase the chances that an expert or fellow user
-reading it will have enough information and motivation to
-reply.</p>
-<p>Make sure you give full details of the problem,
-including:</p>
-<div class=3D"itemizedlist"><ul type=3D"disc">
-<li><p>Exactly what version you are having problems
- with. To find out, run valgrind:
- <tt class=3D"computeroutput">% valgrind --version</tt>
- </p></li>
-<li><p>Which Linux release you're using (Red Hat, Suse, Debian,
- whatever), and what version of that release.</p></li>
-<li><p>The exact and complete text of any error messages
- printed.</p></li>
-<li><p>What version of the kernel and shared libraries you have
- installed. The kernel version can be found by typing
- <tt class=3D"computeroutput">uname -a</tt>, and the shared
- library version by typing=20
- <tt class=3D"computeroutput">ls -l /lib/libc*</tt>.</p></li>
-<li><p>Details of what hardware you're running on.</p></li>
-</ul></div>
-<p>You are in little danger of making your posting too long
-unless you include large chunks of valgrind's (unsuppressed)
-output, so err on the side of giving too much information.</p>
-<p>Use a clear, detailed Subject line. Don't put things like
-"doesn't work", "Valgrind", "help", or "question" in it -- we
-already know that. Use the space for part of an error message, or
-a summary of the unusual behavior.</p>
-<p>Summarize your problem in a short paragarph at the top of
-your posting.</p>
-<p>Finally, remember that, despite the fact that most of the
-community are very helpful and responsive to emailed questions,
-you are probably requesting help from unpaid volunteers, so you
-have no right to expect an answer.</p>
-</div>
-</div>
-<div>
-<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
-<tr>
-<td rowspan=3D"2" width=3D"40%" align=3D"left">
-<a accesskey=3D"p" href=3D"faq.misc.html"><<=A07.=A0Miscellaneous<=
/a>=A0</td>
-<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
-<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"license.gfdl.html">9.=A0The GNU Free Documentation License=A0>&g=
t;</a>
-</td>
-</tr>
-<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
-</table>
-</div>
Deleted: trunk/docs/FAQ/faq.installing.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.installing.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/faq.installing.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,67 +0,0 @@
-<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"faq.background.html"><img src=3D"images/prev.png" width=3D"18" h=
eight=3D"21" border=3D"0" alt=3D"Prev"></a></td>
-<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
-<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
-<th align=3D"center" valign=3D"middle">Valgrind FAQ</th>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"faq.abort.html"><img src=3D"images/next.png" width=3D"18" height=
=3D"21" border=3D"0" alt=3D"Next"></a></td>
-</tr></table></div>
-<div class=3D"sect1" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.installing"></a>3.=A0Compiling, installing and configurin=
g</h2></div></div>
-<div></div>
-</div>
-<div class=3D"qandaset">
-<dl><dt>3.1. <a href=3D"faq.installing.html#faq.make_dies">When I trying=
building Valgrind, 'make' dies partway with
- an assertion failure, something like this:=20
-
-% make: expand.c:489: allocated_variable_append:=20
- Assertion 'current_variable_set_list->next !=3D 0' failed.
-
- </a>
-</dt></dl>
-<table border=3D"0" summary=3D"Q and A Set">
-<col align=3D"left" width=3D"1%">
-<tbody>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.make_dies"></a><a name=3D"id2459790"></a><b>3.1.</b>
-</td>
-<td align=3D"left" valign=3D"top">
-<p>When I trying building Valgrind, 'make' dies partway with
- an assertion failure, something like this:=20
-</p>
-<pre class=3D"screen">
-% make: expand.c:489: allocated_variable_append:=20
- Assertion 'current_variable_set_list->next !=3D 0' failed.
-</pre>
-<p>
- </p>
-</td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top"><p>It's probably a bug in 'make'. Som=
e, but not all,
- instances of version 3.79.1 have this bug, see
- www.mail-archive.com/bug...@gn.../msg01658.html. Try
- upgrading to a more recent version of 'make'. Alternatively,
- we have heard that unsetting the CFLAGS environment variable
- avoids the problem.</p></td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
-<tr>
-<td rowspan=3D"2" width=3D"40%" align=3D"left">
-<a accesskey=3D"p" href=3D"faq.background.html"><<=A02.=A0Backgrou=
nd</a>=A0</td>
-<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
-<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"faq.abort.html">4.=A0Valgrind aborts unexpectedly=A0>></a>
-</td>
-</tr>
-<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
-</table>
-</div>
Deleted: trunk/docs/FAQ/faq.misc.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.misc.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/faq.misc.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,96 +0,0 @@
-<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"faq.notfound.html"><img src=3D"images/prev.png" width=3D"18" hei=
ght=3D"21" border=3D"0" alt=3D"Prev"></a></td>
-<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
-<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
-<th align=3D"center" valign=3D"middle">Valgrind FAQ</th>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"faq.help.html"><img src=3D"images/next.png" width=3D"18" height=3D=
"21" border=3D"0" alt=3D"Next"></a></td>
-</tr></table></div>
-<div class=3D"sect1" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.misc"></a>7.=A0Miscellaneous</h2></div></div>
-<div></div>
-</div>
-<div class=3D"qandaset">
-<dl>
-<dt>7.1. <a href=3D"faq.misc.html#faq.writesupp">I tried writing a suppr=
ession but it didn't work. Can
- you write my suppression for me?</a>
-</dt>
-<dt>7.2. <a href=3D"faq.misc.html#faq.deflost">With Memcheck/Addrcheck's=
memory leak detector, what's
- the difference between "definitely lost", "possibly lost",
- "still reachable", and "suppressed"?</a>
-</dt>
-</dl>
-<table border=3D"0" summary=3D"Q and A Set">
-<col align=3D"left" width=3D"1%">
-<tbody>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.writesupp"></a><a name=3D"id2520582"></a><b>7.1.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>I tried writing a suppression but i=
t didn't work. Can
- you write my suppression for me?</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>Yes! Use the
- <tt class=3D"computeroutput">--gen-suppressions=3Dyes</tt> feature
- to spit out suppressions automatically for you. You can then
- edit them if you like, eg. combining similar automatically
- generated suppressions using wildcards like
- <tt class=3D"literal">'*'</tt>.</p>
-<p>If you really want to write suppressions by hand, read
- the manual carefully. Note particularly that C++ function
- names must be <tt class=3D"literal">_mangled_</tt>.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.deflost"></a><a name=3D"id2520629"></a><b>7.2.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>With Memcheck/Addrcheck's memory le=
ak detector, what's
- the difference between "definitely lost", "possibly lost",
- "still reachable", and "suppressed"?</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>The details are in the Manual:=20
- <a href=3D"http://www.valgrind.org/docs/bookset/mc-main.leaks.html" t=
arget=3D"_top">Memory leak detection</a>.</p>
-<p>In short:</p>
-<div class=3D"itemizedlist"><ul type=3D"disc">
-<li><p>"definitely lost" means your program is leaking memory
- -- fix it!</p></li>
-<li><p>"possibly lost" means your program is probably leaking
- memory, unless you're doing funny things with
- pointers.</p></li>
-<li><p>"still reachable" means your program is probably ok --
- it didn't free some memory it could have. This is quite
- common and often reasonable. Don't use
- <tt class=3D"computeroutput">--show-reachable=3Dyes</tt> if you
- don't want to see these reports.</p></li>
-<li><p>"suppressed" means that a leak error has been
- suppressed. There are some suppressions in the default
- suppression files. You can ignore suppressed errors.</p></li>
-</ul></div>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
-<tr>
-<td rowspan=3D"2" width=3D"40%" align=3D"left">
-<a accesskey=3D"p" href=3D"faq.notfound.html"><<=A06.=A0Memcheck d=
oesn't find my bug</a>=A0</td>
-<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
-<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"faq.help.html">8.=A0How To Get Further Assistance=A0>></a>
-</td>
-</tr>
-<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
-</table>
-</div>
Deleted: trunk/docs/FAQ/faq.notfound.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.notfound.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/faq.notfound.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,131 +0,0 @@
-<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"faq.unexpected.html"><img src=3D"images/prev.png" width=3D"18" h=
eight=3D"21" border=3D"0" alt=3D"Prev"></a></td>
-<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
-<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
-<th align=3D"center" valign=3D"middle">Valgrind FAQ</th>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"faq.misc.html"><img src=3D"images/next.png" width=3D"18" height=3D=
"21" border=3D"0" alt=3D"Next"></a></td>
-</tr></table></div>
-<div class=3D"sect1" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.notfound"></a>6.=A0Memcheck doesn't find my bug</h2></div=
></div>
-<div></div>
-</div>
-<div class=3D"qandaset">
-<dl>
-<dt>6.1. <a href=3D"faq.notfound.html#faq.hiddenbug">I try running "valg=
rind --tool=3Dmemcheck my_program" and
- get Valgrind's startup message, but I don't get any errors and
- I know my program has errors.</a>
-</dt>
-<dt>6.2. <a href=3D"faq.notfound.html#faq.overruns">Why doesn't Memcheck=
find the array overruns in this program?</a>
-</dt>
-<dt>6.3. <a href=3D"faq.notfound.html#faq.segfault">My program dies with=
a segmentation fault, but Memcheck
- doesn't give any error messages before it, or none that look
- related.</a>
-</dt>
-</dl>
-<table border=3D"0" summary=3D"Q and A Set">
-<col align=3D"left" width=3D"1%">
-<tbody>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.hiddenbug"></a><a name=3D"id2520412"></a><b>6.1.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>I try running "valgrind --tool=3Dme=
mcheck my_program" and
- get Valgrind's startup message, but I don't get any errors and
- I know my program has errors.</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>By default, Valgrind only traces the top-level process.
- So if your program spawns children, they won't be traced by
- Valgrind by default. Also, if your program is started by a
- shell script, Perl script, or something similar, Valgrind will
- trace the shell, or the Perl interpreter, or equivalent.</p>
-<p>To trace child processes, use the
- <tt class=3D"literal">--trace-children=3Dyes</tt> option.</p>
-<p>If you are tracing large trees of processes, it can be
- less disruptive to have the output sent over the network. Give
- Valgrind the flag
- <tt class=3D"literal">--log-socket=3D127.0.0.1:12345</tt> (if you want
- logging output sent to <tt class=3D"literal">port 12345</tt> on
- <tt class=3D"literal">localhost</tt>). You can use the
- valgrind-listener program to listen on that port:</p>
-<pre class=3D"programlisting">
-valgrind-listener 12345
-</pre>
-<p>Obviously you have to start the listener process first.
- See the Manual: <a href=3D"http://www.valgrind.org/docs/manual/coregri=
nd_core.html#comment" target=3D"_top">Directing output to file</a> for mo=
re details.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.overruns"></a><a name=3D"id2520493"></a><b>6.2.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>Why doesn't Memcheck find the array=
overruns in this program?</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<pre class=3D"programlisting">
-int static[5];
-
-int main(void)
-{
- int stack[5];
-
- static[5] =3D 0;
- stack [5] =3D 0;
- =20
- return 0;
-}
-</pre>
-<p>Unfortunately, Memcheck doesn't do bounds checking on
- static or stack arrays. We'd like to, but it's just not
- possible to do in a reasonable way that fits with how Memcheck
- works. Sorry.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.segfault"></a><a name=3D"id2520525"></a><b>6.3.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>My program dies with a segmentation=
fault, but Memcheck
- doesn't give any error messages before it, or none that look
- related.</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>One possibility is that your program accesses to memory
- with inappropriate permissions set, such as writing to
- read-only memory. Maybe your program is writing to a static
- string like this:</p>
-<pre class=3D"programlisting">
-char* s =3D "hello";
-s[0] =3D 'j';
-</pre>
-<p>or something similar. Writing to read-only memory can
- also apparently make LinuxThreads behave strangely.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
-<tr>
-<td rowspan=3D"2" width=3D"40%" align=3D"left">
-<a accesskey=3D"p" href=3D"faq.unexpected.html"><<=A05.=A0Valgrind=
behaves unexpectedly</a>=A0</td>
-<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
-<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"faq.misc.html">7.=A0Miscellaneous=A0>></a>
-</td>
-</tr>
-<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
-</table>
-</div>
Deleted: trunk/docs/FAQ/faq.unexpected.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.unexpected.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/faq.unexpected.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,237 +0,0 @@
-<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"faq.abort.html"><img src=3D"images/prev.png" width=3D"18" height=
=3D"21" border=3D"0" alt=3D"Prev"></a></td>
-<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
-<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
-<th align=3D"center" valign=3D"middle">Valgrind FAQ</th>
-<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"faq.notfound.html"><img src=3D"images/next.png" width=3D"18" hei=
ght=3D"21" border=3D"0" alt=3D"Next"></a></td>
-</tr></table></div>
-<div class=3D"sect1" lang=3D"en">
-<div class=3D"titlepage">
-<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.unexpected"></a>5.=A0Valgrind behaves unexpectedly</h2></=
div></div>
-<div></div>
-</div>
-<div class=3D"qandaset">
-<dl>
-<dt>5.1. <a href=3D"faq.unexpected.html#faq.no-output">I try running "va=
lgrind my-program", but my-program runs
- normally, and Valgrind doesn't emit any output at all.</a>
-</dt>
-<dt>5.2. <a href=3D"faq.unexpected.html#faq.slowthread">My threaded serv=
er process runs unbelievably slowly on
- Valgrind. So slowly, in fact, that at first I thought it had
- completely locked up.</a>
-</dt>
-<dt>5.3. <a href=3D"faq.unexpected.html#faq.reports">My program uses the=
C++ STL and string classes. Valgrind
- reports 'still reachable' memory leaks involving these classes
- at the exit of the program, but there should be none.</a>
-</dt>
-<dt>5.4. <a href=3D"faq.unexpected.html#faq.unhelpful">The stack traces =
given by Memcheck (or another tool)
- aren't helpful. How can I improve them?</a>
-</dt>
-</dl>
-<table border=3D"0" summary=3D"Q and A Set">
-<col align=3D"left" width=3D"1%">
-<tbody>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.no-output"></a><a name=3D"id2458918"></a><b>5.1.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>I try running "valgrind my-program"=
, but my-program runs
- normally, and Valgrind doesn't emit any output at all.</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p><span><b class=3D"command">For versions prior to 2.1.1:</b></span></p=
>
-<p>Valgrind doesn't work out-of-the-box with programs that
- are entirely statically linked. It does a quick test at
- startup, and if it detects that the program is statically
- linked, it aborts with an explanation.</p>
-<p>This test may fail in some obscure cases, eg. if you run
- a script under Valgrind and the script interpreter is
- statically linked.</p>
-<p>If you still want static linking, you can ask gcc to link
- certain libraries statically. Try the following options:</p>
-<pre class=3D"screen">
--Wl,-Bstatic -lmyLibrary1 -lotherLibrary -Wl,-Bdynamic
-</pre>
-<p>Just make sure you end with
- <tt class=3D"computeroutput">-Wl,-Bdynamic</tt> so that libc is
- dynamically linked.</p>
-<p>If you absolutely cannot use dynamic libraries, you can
- try statically linking together all the .o files in coregrind/,
- all the .o files of the tool of your choice (eg. those in
- memcheck/), and the .o files of your program. You'll end up
- with a statically linked binary that runs permanently under
- Valgrind's control. Note that we haven't tested this procedure
- thoroughly.</p>
-<p><span><b class=3D"command">For versions 2.1.1 and later:</b></span></=
p>
-<p>Valgrind does now work with static binaries, although
- beware that some of the tools won't operate as well as normal,
- because they have access to less information about how the
- program runs. Eg. Memcheck will miss some errors that it would
- otherwise find. This is because Valgrind doesn't replace
- malloc() and friends with its own versions. It's best if your
- program is dynamically linked with glibc.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.slowthread"></a><a name=3D"id2459006"></a><b>5.2.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>My threaded server process runs unb=
elievably slowly on
- Valgrind. So slowly, in fact, that at first I thought it had
- completely locked up.</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>We are not completely sure about this, but one
- possibility is that laptops with power management fool
- Valgrind's timekeeping mechanism, which is (somewhat in error)
- based on the x86 RDTSC instruction. A "fix" which is claimed
- to work is to run some other cpu-intensive process at the same
- time, so that the laptop's power-management clock-slowing does
- not kick in. We would be interested in hearing more feedback
- on this.</p>
-<p>Another possible cause is that versions prior to 1.9.6
- did not support threading on glibc 2.3.X systems well.
- Hopefully the situation is much improved with 1.9.6 and later
- versions.</p>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.reports"></a><a name=3D"id2459042"></a><b>5.3.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>My program uses the C++ STL and str=
ing classes. Valgrind
- reports 'still reachable' memory leaks involving these classes
- at the exit of the program, but there should be none.</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>First of all: relax, it's probably not a bug, but a
- feature. Many implementations of the C++ standard libraries
- use their own memory pool allocators. Memory for quite a
- number of destructed objects is not immediately freed and given
- back to the OS, but kept in the pool(s) for later re-use. The
- fact that the pools are not freed at the exit() of the program
- cause Valgrind to report this memory as still reachable. The
- behaviour not to free pools at the exit() could be called a bug
- of the library though.</p>
-<p>Using gcc, you can force the STL to use malloc and to
- free memory as soon as possible by globally disabling memory
- caching. Beware! Doing so will probably slow down your
- program, sometimes drastically.</p>
-<div class=3D"itemizedlist"><ul type=3D"disc">
-<li><p>With gcc 2.91, 2.95, 3.0 and 3.1, compile all source
- using the STL with <tt class=3D"literal">-D__USE_MALLOC</tt>. Beware=
!
- This is removed from gcc starting with version 3.3.</p></li>
-<li><p>With gcc 3.2.2 and later, you should export the environment
- variable <tt class=3D"literal">GLIBCPP_FORCE_NEW</tt> before running
- your program.</p></li>
-<li><p>With gcc 3.4 and later, that variable has changed name to
- <tt class=3D"literal">GLIBCXX_FORCE_NEW</tt>.</p></li>
-</ul></div>
-<p>There are other ways to disable memory pooling: using the
- <tt class=3D"literal">malloc_alloc</tt> template with your objects (no=
t
- portable, but should work for gcc) or even writing your own
- memory allocators. But all this goes beyond the scope of this
- FAQ. Start by reading <a href=3D"http://gcc.gnu.org/onlinedocs/libstd=
c++/ext/howto.html" target=3D"_top">
- http://gcc.gnu.org/onlinedocs/libstdc++/ext/howto.html</a>
- if you absolutely want to do that. But beware:</p>
-<div class=3D"orderedlist"><ol type=3D"1">
-<li><p>there are currently changes underway for gcc which are
- not totally reflected in the docs right now ("now" =3D=3D 26 Apr
- 03)</p></li>
-<li><p>allocators belong to the more messy parts of the STL
- and people went to great lengths to make it portable across
- platforms. Chances are good that your solution will work on
- your platform, but not on others.</p></li>
-</ol></div>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-<tr class=3D"question">
-<td align=3D"left" valign=3D"top">
-<a name=3D"faq.unhelpful"></a><a name=3D"id2520280"></a><b>5.4.</b>
-</td>
-<td align=3D"left" valign=3D"top"><p>The stack traces given by Memcheck =
(or another tool)
- aren't helpful. How can I improve them?</p></td>
-</tr>
-<tr class=3D"answer">
-<td>=A0</td>
-<td align=3D"left" valign=3D"top">
-<p>If they're not long enough, use
- <tt class=3D"literal">--num-callers</tt> to make them longer.</p>
-<p>If they're not detailed enough, make sure you are
- compiling with <tt class=3D"literal">-g</tt> to add debug information.
- And don't strip symbol tables (programs should be unstripped
- unless you run 'strip' on them; some libraries ship
- stripped).</p>
-<p>Also, for leak reports involving shared objects, if the shared object=
is
- unloaded before the program terminates, Valgrind will discard the debu=
g
- information and the error message will be full of
- <tt class=3D"literal">???</tt> entries. The workaround here is to avo=
id
- calling <tt class=3D"literal">dlclose()</tt> on these shared objects.<=
/p>
-<p>Also, <tt class=3D"literal">-fomit-frame-pointer</tt> and
- <tt class=3D"literal">-fstack-check</tt> can make stack traces
- worse.</p>
-<p>Some example sub-traces:</p>
-<p>With debug information and unstripped (best):</p>
-<pre class=3D"programlisting">
-Invalid write of size 1
- at 0x80483BF: really (malloc1.c:20)
- by 0x8048370: main (malloc1.c:9)
-</pre>
-<p>With no debug information, unstripped:</p>
-<pre class=3D"programlisting">
-Invalid write of size 1
- at 0x80483BF: really (in /auto/homes/njn25/grind/head5/a.out)
- by 0x8048370: main (in /auto/homes/njn25/grind/head5/a.out)
-</pre>
-<p>With no debug information, stripped:</p>
-<pre class=3D"programlisting">
-Invalid write of size 1
- at 0x80483BF: (within /auto/homes/njn25/grind/head5/a.out)
- by 0x8048370: (within /auto/homes/njn25/grind/head5/a.out)
- by 0x42015703: __libc_start_main (in /lib/tls/libc-2.3.2.so)
- by 0x80482CC: (within /auto/homes/njn25/grind/head5/a.out)
-</pre>
-<p>With debug information and -fomit-frame-pointer:</p>
-<pre class=3D"programlisting">
-Invalid write of size 1
- at 0x80483C4: really (malloc1.c:20)
- by 0x42015703: __libc_start_main (in /lib/tls/libc-2.3.2.so)
- by 0x80482CC: ??? (start.S:81)
-</pre>
-<p>A leak error message involving an unloaded shared object:</p>
-<pre class=3D"programlisting">
-84 bytes in 1 blocks are possibly lost in loss record 488 of 713
- at 0x1B9036DA: operator new(unsigned) (vg_replace_malloc.c:132)
- by 0x1DB63EEB: ???
- by 0x1DB4B800: ???
- by 0x1D65E007: ???
- by 0x8049EE6: main (main.cpp:24)
-</pre>
-</td>
-</tr>
-<tr><td colspan=3D"2">=A0</td></tr>
-</tbody>
-</table>
-</div>
-</div>
-<div>
-<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
-<tr>
-<td rowspan=3D"2" width=3D"40%" align=3D"left">
-<a accesskey=3D"p" href=3D"faq.abort.html"><<=A04.=A0Valgrind abor=
ts unexpectedly</a>=A0</td>
-<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
-<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"faq.notfound.html">6.=A0Memcheck doesn't find my bug=A0>></a>
-</td>
-</tr>
-<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
-</table>
-</div>
Modified: trunk/docs/FAQ/index.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/index.html 2005-08-03 22:44:55 UTC (rev 160)
+++ trunk/docs/FAQ/index.html 2005-08-03 22:57:01 UTC (rev 161)
@@ -1,106 +1,654 @@
-<div></div>
-<div class=3D"article" lang=3D"en">
+<div class=3D"book" lang=3D"en">
<div class=3D"titlepage">
<div>
<div><h1 class=3D"title">
-<a name=3D"faq"></a>Valgrind FAQ</h1></div>
-<div><h3 class=3D"subtitle"><i>Valgrind Frequently Asked Questions</i></=
h3></div>
+<a name=3D"FAQ"></a>Valgrind FAQ</h1></div>
+<div><h2 class=3D"subtitle">Valgrind Frequently Asked Questions</h2></di=
v>
<div><div class=3D"author">
<h3 class=3D"author"><span class=3D"surname">
- <a href=3D"http://www.valgrind.org/info/developers.html" target=3D=
"_top">Valgrind Developers</a>
+ <a href=3D"http://www.valgrind.org/www/developers.html" target=3D"=
_top">Valgrind Developers</a>
</span></h3>
<div class=3D"affiliation"><span class=3D"orgname">
<a href=3D"mailto:val...@va..." target=3D"_top">valgrind@=
valgrind.org</a>
<br></span></div>
</div></div>
-<div><p class=3D"releaseinfo">Revision 2.1.4 of August 25 2004</p></div>
+<div><p class=3D"releaseinfo">August 3 2005</p></div>
</div>
+<div></div>
<hr>
</div>
-<div class=3D"toc">
-<p><b>Table of Contents</b></p>
+<div class=3D"sect1" lang=3D"en">
+<div class=3D"titlepage">
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"faq.background"></a>1.=A0Background</h2></div></div>
+<div></div>
+</div>
+<div class=3D"qandaset">
<dl>
-<dt><span class=3D"sect1"><a href=3D"index.html#faq.intro">1. Introducti=
on</a></span></dt>
-<dd><dl>
-<dt><span class=3D"sect2"><a href=3D"index.html#faq.about">1.1. About th=
e FAQ</a></span></dt>
-<dt><span class=3D"sect2"><a href=3D"index.html#faq.comments">1.2. Where=
To Send Questions</a></span></dt>
-<dt><span class=3D"sect2"><a href=3D"index.html#faq.copyright">1.3. Copy=
right and License</a></span></dt>
-</dl></dd>
-<dt><span class=3D"sect1"><a href=3D"faq.background.html">2. Background<=
/a></span></dt>
-<dt><span class=3D"sect1"><a href=3D"faq.installing.html">3. Compiling, =
installing and configuring</a></span></dt>
-<dt><span class=3D"sect1"><a href=3D"faq.abort.html">4. Valgrind aborts =
unexpectedly</a></span></dt>
-<dt><span class=3D"sect1"><a href=3D"faq.unexpected.html">5. Valgrind be=
haves unexpectedly</a></span></dt>
-<dt><span class=3D"sect1"><a href=3D"faq.notfound.html">6. Memcheck does=
n't find my bug</a></span></dt>
-<dt><span class=3D"sect1"><a href=3D"faq.misc.html">7. Miscellaneous</a>=
</span></dt>
-<dt><span class=3D"sect1"><a href=3D"faq.help.html">8. How To Get Furthe=
r Assistance</a></span></dt>
-<dd><dl>
-<dt><span class=3D"sect2"><a href=3D"faq.help.html#faq.unanswered">8.1. =
If Your Question Still Isn't Answered ...</a></span></dt>
-<dt><span class=3D"sect2"><a href=3D"faq.help.html#faq.request">8.2. Wha=
t to Put in a Request for Help</a></span></dt>
-</dl></dd>
-<dt><span class=3D"sect1"><a href=3D"license.gfdl.html">9. The GNU Free =
Documentation License</a></span></dt>
+<dt>1.1. <a href=3D"FAQ.html#faq.pronounce">How do you pronounce "Valgri=
nd"?</a>
+</dt>
+<dt>1.2. <a href=3D"FAQ.html#faq.whence">Where does the name "Valgrind" =
come from?</a>
+</dt>
</dl>
+<table border=3D"0" summary=3D"Q and A Set">
+<col align=3D"left" width=3D"1%">
+<tbody>
+<tr class=3D"question">
+<td align=3D"left" valign=3D"top">
+<a name=3D"faq.pronounce"></a><a name=3D"id4869828"></a><b>1.1.</b>
+</td>
+<td align=3D"left" valign=3D"top"><p>How do you pronounce "Valgrind"?</p=
></td>
+</tr>
+<tr class=3D"answer">
+<td>=A0</td>
+<td align=3D"left" valign=3D"top">
+<p>The "Val" as in the world "value". The "grind" is
+ pronounced with a short 'i' -- ie. "grinned" (rhymes with
+ "tinned") rather than "grined" (rhymes with "find").</p>
+<p>Don't feel bad: almost everyone gets it wrong at
+ first.</p>
+</td>
+</tr>
+<tr><td colspan=3D"2">=A0</td></tr>
+<tr class=3D"question">
+<td align=3D"left" valign=3D"top">
+<a name=3D"faq.whence"></a><a name=3D"id4834215"></a><b>1.2.</b>
+</td>
+<td align=3D"left" valign=3D"top"><p>Where does the name "Valgrind" come=
from?</p></td>
+</tr>
+<tr class=3D"answer">
+<td>=A0</td>
+<td align=3D"left" valign=3D"top">
+<p>From Nordic mythology. Originally (before release) the
+ project was named Heimdall, after the watchman of the Nordic
+ gods. He could "see a hundred miles by day or night, hear the
+ grass growing, see the wool growing on a sheep's back" (etc).
+ This would have been a great name, but it was already taken by
+ a security package "Heimdal".</p>
+<p>Keeping with the
+ Nordic theme, Valgrind was chosen. Valgrind is the name of the
+ main entrance to Valhalla (the Hall of the Chosen Slain in
+ Asgard). Over this entrance there resides a wolf and over it
+ there is the head of a boar and on it perches a huge eagle,
+ whose eyes can see to the far regions of the nine worlds. Only
+ those judged worthy by the guardians are allowed to pass
+ through Valgrind. All others are refused entrance.</p>
+<p>It's not short for "value grinder", although that's not a
+ bad guess.</p>
+</td>
+</tr>
+<tr><td colspan=3D"2">=A0</td></tr>
+</tbody>
+</table>
</div>
+</div>
<div class=3D"sect1" lang=3D"en">
<div class=3D"titlepage">
<div><div><h2 class=3D"title" style=3D"clear: both">
-<a name=3D"faq.intro"></a>1.=A0Introduction</h2></div></div>
+<a name=3D"faq.installing"></a>2.=A0Compiling, installing and configurin=
g</h2></div></div>
<div></div>
</div>
-<div class=3D"sect2" lang=3D"en">
+<div class=3D"qandaset">
+<dl><dt>2.1. <a href=3D"FAQ.html#faq.make_dies">When I trying building V=
algrind, 'make' dies partway with
+ an assertion failure, something like this:=20
+
+% make: expand.c:489: allocated_variable_append:=20
+ Assertion 'current_variable_set_list->next !=3D 0' failed.
+
+ </a>
+</dt></dl>
+<table border=3D"0" summary=3D"Q and A Set">
+<col align=3D"left" width=3D"1%">
+<tbody>
+<tr class=3D"question">
+<td align=3D"left" valign=3D"top">
+<a name=3D"faq.make_dies"></a><a name=3D"id4817600"></a><b>2.1.</b>
+</td>
+<td align=3D"left" valign=3D"top">
+<p>When I trying building Valgrind, 'make' dies partway with
+ an assertion failure, something like this:=20
+</p>
+<pre class=3D"screen">
+% make: expand.c:489: allocated_variable_append:=20
+ Assertion 'current_variable_set_list->next !=3D 0' failed.
+</pre>
+<p>
+ </p>
+</td>
+</tr>
+<tr class=3D"answer">
+<td>=A0</td>
+<td align=3D"left" valign=3D"top"><p>It's probably a bug in 'make'. Som=
e, but not all,
+ instances of version 3.79.1 have this bug, see
+ www.mail-archive.com/bug...@gn.../msg01658.html. Try
+ upgrading to a more recent version of 'make'. Alternatively,
+ we have heard that unsetting the CFLAGS environment variable
+ avoids the problem.</p></td>
+</tr>
+<tr><td colspan=3D"2">=A0</td></tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class=3D"sect1" lang=3D"en">
<div class=3D"titlepage">
-<div><div><h3 class=3D"title">
-<a name=3D"faq.about"></a>1.1.=A0About the FAQ</h3></div></div>
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"faq.abort"></a>3.=A0Valgrind aborts unexpectedly</h2></div></=
div>
<div></div>
</div>
-<p>This document contains a collection of answers to the most
-common questions people ask about Valgrind.</p>
-<p>The latest version is available from=20
-<a href=3D"http://www.valgrind.org" target=3D"_top">http://www.valgrind.=
org</a>.</p>
-<p><span><b class=3D"command">Disclaimer:</b></span> While every attempt=
has been
-made to provide accurate and helpful information, we make no
-promises or guarantees of any kind. Use this information at your
-own risk.</p>
+<div class=3D"qandaset">
+<dl>
+<dt>3.1. <a href=3D"FAQ.html#faq.exit_errors">Programs run OK on Valgrin=
d, but at exit produce a bunch
+ of errors a bit like this:</a>
+</dt>
+<dt>3.2. <a href=3D"FAQ.html#faq.bugdeath">My (buggy) program dies like =
this:</a>
+</dt>
+<dt>3.3. <a href=3D"FAQ.html#faq.msgdeath">My program dies, printing a m=
essage like this along the
+ way:</a>
+</dt>
+</dl>
+<table border=3D"0" summary=3D"Q and A Set">
+<col align=3D"left" width=3D"1%">
+<tbody>
+<tr class=3D"question">
+<td align=3D"left" valign=3D"top">
+<a name=3D"faq.exit_errors"></a><a name=3D"id4817647"></a><b>3.1.</b>
+</td>
+<td align=3D"left" valign=3D"top"><p>Programs run OK on Valgrind, but at=
exit produce a bunch
+ of errors a bit like this:</p></td>
+</tr>
+<tr class=3D"answer">
+<td>=A0</td>
+<td align=3D"left" valign=3D"top">
+<p>
+</p>
+<pre class=3D"programlisting">
+=3D=3D20755=3D=3D Invalid read of size 4
+=3D=3D20755=3D=3D at 0x40281C8A: _nl_unload_locale (loadlocale.c:238)
+=3D=3D20755=3D=3D by 0x4028179D: free_mem (findlocale.c:257)
+=3D=3D20755=3D=3D by 0x402E0962: __libc_freeres (set-freeres.c:34)
+=3D=3D20755=3D=3D by 0x40048DCC: vgPlain___libc_freeres_wrapper (vg_c=
lientfuncs.c:585)
+=3D=3D20755=3D=3D Address 0x40CC304C is 8 bytes inside a block of siz=
e 380 free'd
+=3D=3D20755=3D=3D at 0x400484C9: free (vg_clientfuncs.c:180)
+=3D=3D20755=3D=3D by 0x40281CBA: _nl_unload_locale (loadlocale.c:246)
+=3D=3D20755=3D=3D by 0x40281218: free_mem (setlocale.c:461)
+=3D=3D20755=3D=3D by 0x402E0962: __libc_freeres (set-freeres.c:34)
+</pre>
+<p>
+
+ and then die with a segmentation fault.</p>
+<p>When the program exits, Valgrind runs the procedure
+ <tt class=3D"literal">__libc_freeres()</tt> in glibc. This is a hook
+ for memory debuggers, so they can ask glibc to free up any
+ memory it has used. Doing that is needed to ensure that
+ Valgrind doesn't incorrectly report space leaks in glibc.</p>
+<p>Problem is that running
+ <tt class=3D"literal">__libc_freeres()</tt> in older glibc versions
+ causes this crash.</p>
+<p>WORKAROUND FOR 1.1.X and later
+ versions of Valgrind: use the
+ <tt class=3D"literal">--run-libc-freeres=3Dno</tt> flag. You may then =
get
+ space leak reports for glibc-allocations (please _don't_ report
+ these to the glibc people, since they are not real leaks), but
+ at least the program runs.</p>
+</td>
+</tr>
+<tr><td colspan=3D"2">=A0</td></tr>
+<tr class=3D"question">
+<td align=3D"left" valign=3D"top">
+<a name=3D"faq.bugdeath"></a><a name=3D"id4828813"></a><b>3.2.</b>
+</td>
+<td align=3D"left" valign=3D"top"><p>My (buggy) program dies like this:<=
/p></td>
+</tr>
+<tr class=3D"answer">
+<td>=A0</td>
+<td align=3D"left" valign=3D"top">
+<pre class=3D"screen">
+% valgrind: vg_malloc2.c:442 (bszW_to_pszW): Assertion 'pszW >=3D 0' =
failed.
+</pre>
+<p>If Memcheck (the memory checker) shows any invalid reads,
+ invalid writes and invalid frees in your program, the above may
+ happen. Reason is that your program may trash Valgrind's
+ low-level memory manager, which then dies with the above
+ assertion, or something like this. The cure is to fix your
+ program so that it doesn't do any illegal memory accesses. The
+ above failure will hopefully go away after that.</p>
+</td>
+</tr>
+<tr><td colspan=3D"2">=A0</td></tr>
+<tr class=3D"question">
+<td align=3D"left" valign=3D"top">
+<a name=3D"faq.msgdeath"></a><a name=3D"id4783893"></a><b>3.3.</b>
+</td>
+<td align=3D"left" valign=3D"top"><p>My program dies, printing a message=
like this along the
+ way:</p></td>
+</tr>
+<tr class=3D"answer">
+<td>=A0</td>
+<td align=3D"left" valign=3D"top">
+<pre class=3D"screen">
+% disInstr: unhandled instruction bytes: 0x66 0xF 0x2E 0x5
+</pre>
+<p>Older versions did not support some x86 instructions,
+ particularly SSE/SSE2 instructions. Try a newer Valgrind; we
+ now support almost all instructions. If it still happens with
+ newer versions, if the failing instruction is an SSE/SSE2
+ instruction, you might be able to recompile your program
+ without it by using the flag
+ <tt class=3D"computeroutput">-march</tt> to gcc. Either way,
+ let us know and we'll try to fix it.</p>
+<p>Another possibility is that your program has a bug and
+ erroneously jumps to a non-code address, in which case you'll
+ get a SIGILL signal. Memcheck/Addrcheck may issue a warning
+ just before this happens, but they might not if the jump
+ happens to land in addressable memory.</p>
+</td>
+</tr>
+<tr><td colspan=3D"2">=A0</td></tr>
+</tbody>
+</table>
</div>
-<div class=3D"sect2" lang=3D"en">
+</div>
+<div class=3D"sect1" lang=3D"en">
<div class=3D"titlepage">
-<div><div><h3 class=3D"title">
-<a name=3D"faq.comments"></a>1.2.=A0Where To Send Questions</h3></div></=
div>
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"faq.unexpected"></a>4.=A0Valgrind behaves unexpectedly</h2></=
div></div>
<div></div>
</div>
-<p>If you have a question about Valgrind that was not answered
-here, or any comments, feel free to send it to the us at=20
-<a href=3D"mailto:val...@va..." target=3D"_top">valgrind@valgri=
nd.org</a>. We won't
-guarantee to answer all questions, but we will answer as many as
-we can. Questions that we receive repeatedly will be added to
-this FAQ. If you wish to refer to a question in the FAQ, please
-include the title of the question in your email.</p>
-<p>If you have an addition to the FAQ, by all means send
-it. Contributions may be in any format, but we infinitely prefer
-plain text.</p>
+<div class=3D"qandaset">
+<dl>
+<dt>4.1. <a href=3D"FAQ.html#faq.slowthread">My threaded server process =
runs unbelievably slowly on
+ Valgrind. So slowly, in fact, that at first I thought it had
+ completely locked up.</a>
+</dt>
+<dt>4.2. <a href=...
[truncated message content] |
|
From: <sv...@va...> - 2005-08-03 22:44:56
|
Author: de Date: 2005-08-03 23:44:55 +0100 (Wed, 03 Aug 2005) New Revision: 160 Log: oops - forgot to prune the nav stuff Modified: trunk/docs/quick-start.html Modified: trunk/docs/quick-start.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/quick-start.html 2005-08-03 22:42:35 UTC (rev 159) +++ trunk/docs/quick-start.html 2005-08-03 22:44:55 UTC (rev 160) @@ -1,10 +1,3 @@ -<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D= "3" border=3D"0" summary=3D"Navigation header"><tr> -<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"= href=3D"index.html"><img src=3D"images/prev.png" width=3D"18" height=3D"= 21" border=3D"0" alt=3D"Prev"></a></td> -<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"= href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18= " border=3D"0" alt=3D"Up"></a></td> -<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"= href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"= 20" border=3D"0" alt=3D"Up"></a></td> -<th align=3D"center" valign=3D"middle">Valgrind Documentation</th> -<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"= href=3D"manual.html"><img src=3D"images/next.png" width=3D"18" height=3D= "21" border=3D"0" alt=3D"Next"></a></td> -</tr></table></div> <div class=3D"book" lang=3D"en"> <div class=3D"titlepage"> <div><div><h1 class=3D"title"> @@ -192,15 +185,3 @@ <tt class=3D"computeroutput">--tool</tt> option.</p> </div> </div> -<div> -<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D= "2" border=3D"0" summary=3D"Navigation footer"> -<tr> -<td rowspan=3D"2" width=3D"40%" align=3D"left"> -<a accesskey=3D"p" href=3D"index.html"><<=A0Valgrind Documentation= </a>=A0</td> -<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html= ">Up</a></td> -<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr= ef=3D"manual.html">Valgrind User Manual=A0>></a> -</td> -</tr> -<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.= html">Home</a></td></tr> -</table> -</div> |
|
From: <sv...@va...> - 2005-08-03 22:42:37
|
Author: de
Date: 2005-08-03 23:42:35 +0100 (Wed, 03 Aug 2005)
New Revision: 159
Log:
updated doc
Modified:
trunk/docs/quick-start.html
Modified: trunk/docs/quick-start.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/quick-start.html 2005-08-03 22:39:44 UTC (rev 158)
+++ trunk/docs/quick-start.html 2005-08-03 22:42:35 UTC (rev 159)
@@ -1,166 +1,206 @@
-<h1>Valgrind Quick Start</h1>
-
-<p>The Valgrind distribution has multiple tools. The memory
-checking tool (called Memcheck) can detect many common memory
-errors such as:</p>
-
-<ul>
-
- <li>touching memory you shouldn't (eg. overrunning heap block
- boundaries)</li>
-
- <li>using values before they have been initialized</li>
-
- <li>incorrect freeing of memory, such as double-freeing heap
- blocks</li>
-
- <li>memory leaks</li>
-
-</ul>
-
-<p>What follows is the minimum information you need to start
-detecting memory errors in your program with Memcheck. Note that
-this guide applies to Valgrind version 2.4.0; some of the
-information is not quite right for earlier versions.</p>
-
-
-<h3>1. Preparing your program.</h3>
-
-<p>Compile your program with <code>-g</code> to include debugging
-information so that Memcheck's error messages include exact line
+<div><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"3" border=3D"0" summary=3D"Navigation header"><tr>
+<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"p"=
href=3D"index.html"><img src=3D"images/prev.png" width=3D"18" height=3D"=
21" border=3D"0" alt=3D"Prev"></a></td>
+<td width=3D"25px" align=3D"center" valign=3D"middle"><a accesskey=3D"u"=
href=3D"index.html"><img src=3D"images/up.png" width=3D"21" height=3D"18=
" border=3D"0" alt=3D"Up"></a></td>
+<td width=3D"31px" align=3D"center" valign=3D"middle"><a accesskey=3D"h"=
href=3D"index.html"><img src=3D"images/home.png" width=3D"27" height=3D"=
20" border=3D"0" alt=3D"Up"></a></td>
+<th align=3D"center" valign=3D"middle">Valgrind Documentation</th>
+<td width=3D"22px" align=3D"center" valign=3D"middle"><a accesskey=3D"n"=
href=3D"manual.html"><img src=3D"images/next.png" width=3D"18" height=3D=
"21" border=3D"0" alt=3D"Next"></a></td>
+</tr></table></div>
+<div class=3D"book" lang=3D"en">
+<div class=3D"titlepage">
+<div><div><h1 class=3D"title">
+<a name=3D"quick-start"></a>Valgrind Quick Start Guide</h1></div></div>
+<div></div>
+<hr>
+</div>
+<p>The Valgrind distribution has multiple tools. The most popular is th=
e
+memory checking tool (called Memcheck) which can detect many common memo=
ry
+errors such as:
+</p>
+<div class=3D"itemizedlist"><ul type=3D"disc">
+<li><p>touching memory you shouldn't (eg. overrunning heap block=20
+ boundaries);</p></li>
+<li><p>using values before they have been initialized;</p></li>
+<li><p>incorrect freeing of memory, such as double-freeing heap
+ blocks;</p></li>
+<li><p>memory leaks;</p></li>
+</ul></div>
+<p>What follows is the minimum information you need to start detecting
+memory errors in your program with Memcheck. Note that this guide appli=
es
+to Valgrind version 2.4.0 and later; some of the information is not qui=
te
+right for earlier versions.</p>
+<div class=3D"sect1" lang=3D"en">
+<div class=3D"titlepage">
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"quick-start.prepare"></a>1.=A0Preparing your program</h2></di=
v></div>
+<div></div>
+</div>
+<p>Compile your program with <tt class=3D"computeroutput">-g</tt> to inc=
lude
+debugging information so that Memcheck's error messages include exact li=
ne
numbers.</p>
+</div>
+<div class=3D"sect1" lang=3D"en">
+<div class=3D"titlepage">
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"quick-start.mcrun"></a>2.=A0Running your program under Memche=
ck</h2></div></div>
+<div></div>
+</div>
+<p>If you normally run your program like this:
=20
+</p>
+<pre class=3D"programlisting">
+ myprog arg1 arg2
+</pre>
+<p>
=20
-<h3>2. Running your program under Memcheck.</h3>
+Use this command line:
=20
-<p>If you normally run your program like this:=20
-<code>myprog arg1 arg2</code></p>
+</p>
+<pre class=3D"programlisting">
+ valgrind --leak-check=3Dyes myprog arg1 arg2
+</pre>
+<p>
=20
-<p>Use this command line:=20
-<code>valgrind --leak-check=3Dyes myprog arg1 arg2</code></p>
+Memcheck is the default tool. The
+<tt class=3D"computeroutput">--leak-check</tt> option turns on the detai=
led
+memory leak detector.</p>
+<p>Your program will run much slower (eg. 20 to 30 times) than normal,
+and use a lot more memory. Memcheck will issue messages about memory er=
rors
+and leaks that it detects.</p>
+</div>
+<div class=3D"sect1" lang=3D"en">
+<div class=3D"titlepage">
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"quick-start.interpret"></a>3.=A0Interpreting Memcheck's outpu=
t</h2></div></div>
+<div></div>
+</div>
+<p>Here's an example C program with a memory error and a memory leak.
=20
-<p>Memcheck is the default tool. The <code>--leak-check</code>
-option turns on the memory leak detector.</p>
+</p>
+<pre class=3D"programlisting">
+ #include <stdlib.h>
=20
-<p>Your program will run much slower (eg. 20 to 30 times) than
-normal, and use a lot more memory. Memcheck will issue messages
-about memory errors and leaks that it detects.</p>
+ void f(void)
+ {
+ int* x =3D malloc(10 * sizeof(int));
+ x[10] =3D 0; // problem 1: heap block overrun
+ } // problem 2: memory leak -- x not freed
=20
-
-<h3>3. Interpreting Memcheck's output.</h3>
-
-<p>Here's an example C program with a memory errors and a memory
-leak.</p>
-
-<pre>
-#include <stdlib.h>
-
-void f(void) {
- int* x =3D malloc(10 * sizeof(int));
- x[10] =3D 0; // problem 1: heap block overrun
-} // problem 2: memory leak -- x not freed
-
-int main(void) {
- f();
- return 0;
-}
+ int main(void)
+ {
+ f();
+ return 0;
+ }
</pre>
+<p>
=20
-<p>Most error messages look like the following, which describes
-problem 1, the heap block overrun:</p>
+Most error messages look like the following, which describes problem 1, =
the
+heap block overrun:
=20
-<pre>
- =3D=3D19182=3D=3D Invalid write of size 4
- =3D=3D19182=3D=3D at 0x804838F: f (example.c:8)
- =3D=3D19182=3D=3D by 0x80483AB: main (example.c:14)
- =3D=3D19182=3D=3D Address 0x1BA45050 is 0 bytes after a block of size =
40 alloc'd
- =3D=3D19182=3D=3D at 0x1B8FF5CD: malloc (vg_replace_malloc.c:130)
- =3D=3D19182=3D=3D by 0x8048385: f (example.c:7)
- =3D=3D19182=3D=3D by 0x80483AB: main (example.c:14)
+</p>
+<pre class=3D"programlisting">
+ =3D=3D19182=3D=3D Invalid write of size 4
+ =3D=3D19182=3D=3D at 0x804838F: f (example.c:6)
+ =3D=3D19182=3D=3D by 0x80483AB: main (example.c:11)
+ =3D=3D19182=3D=3D Address 0x1BA45050 is 0 bytes after a block of size=
40 alloc'd
+ =3D=3D19182=3D=3D at 0x1B8FF5CD: malloc (vg_replace_malloc.c:130)
+ =3D=3D19182=3D=3D by 0x8048385: f (example.c:5)
+ =3D=3D19182=3D=3D by 0x80483AB: main (example.c:11)
</pre>
+<p>
=20
+Things to notice:
=20
-<p>Things to notice:</p>
+</p>
+<div class=3D"itemizedlist"><ul type=3D"disc">
+<li><p>There is a lot of information in each error message; read it
+ carefully.</p></li>
+<li><p>The 19182 is the process ID; it's usually unimportant.</p></li>
+<li><p>The first line ("Invalid write...") tells you what kind of error =
it
+ is. Here, the program wrote to some memory it should not have due to a
+ heap block overrun.</p></li>
+<li><p>Below the first line is a stack trace telling you where the probl=
em
+ occurred. Stack traces can get quite large, and be confusing, especi=
ally
+ if you are using the C++ STL. Reading them from the bottom up can he=
lp.
+ If the stack trace is not big enough, use the
+ <tt class=3D"computeroutput">--num-callers</tt> option to make it
+ bigger.</p></li>
+<li><p>The addresses (eg. 0x804838F) are usually unimportant, but occasi=
onally
+ crucial for tracking down weirder bugs.</p></li>
+<li><p>Some error messages have a second component which describes the m=
emory
+ address involved. This one shows that the written memory is just pas=
t
+ the end of a block allocated with malloc() on line 7 of example.c.</p=
></li>
+</ul></div>
+<p>
=20
-<ul>
+It's worth fixing errors in the order they are reported, as later
+errors can be caused by earlier errors.</p>
+<p>Memory leak messages look like this:
=20
-<li>There is a lot of information in each error message; read it
- carefully.</li>
-
-<li>The 19182 is the process ID; it's usually unimportant.</li>
-
-<li>The first line ("Invalid write...") tells you what the error
- is. Here, the program wrote to some memory it should not have
- due to a heap block overrun.</li>
-
-<li>Below the first line is a stack trace telling you where the
- problem occurred. Stack traces can get quite large, and be
- confusing, especially if you are using the C++ STL. Reading
- them from the bottom up can help. If the stack trace is not
- big enough, use a bigger <code>--num-callers</code>
- option.</li>
-
-<li>The addresses (eg. 0x804838F) are usually unimportant, but
- occasionally crucial for tracking down weirder bugs.</li>
-
-<li>Some error messages have a second component which describes
- the memory address involved. This one shows that the written
- memory is just past the end of a block allocated with malloc()
- on line 7 of example.c.</li>
-
-</ul>
-
-<p>It's worth fixing errors in the order they are reported, as
-later errors can be caused by earlier errors.</p>
-
-<p>Memory leak messages look like this:</p>
-<pre>
- =3D=3D19182=3D=3D 40 bytes in 1 blocks are definitely lost in loss reco=
rd 1 of 1
- =3D=3D19182=3D=3D at 0x1B8FF5CD: malloc (vg_replace_malloc.c:130)
- =3D=3D19182=3D=3D by 0x8048385: f (a.c:7)
- =3D=3D19182=3D=3D by 0x80483AB: main (a.c:14)
+</p>
+<pre class=3D"programlisting">
+ =3D=3D19182=3D=3D 40 bytes in 1 blocks are definitely lost in loss rec=
ord 1 of 1
+ =3D=3D19182=3D=3D at 0x1B8FF5CD: malloc (vg_replace_malloc.c:130)
+ =3D=3D19182=3D=3D by 0x8048385: f (a.c:7)
+ =3D=3D19182=3D=3D by 0x80483AB: main (a.c:14)
</pre>
+<p>
=20
-<p>The stack trace tells you where the leaked memory was
-allocated. Memcheck cannot tell you why the memory leaked,
-unfortunately. (Ignore the "vg_replace_malloc.c", that's an
-implementation detail.)</p>
+The stack trace tells you where the leaked memory was allocated.
+Memcheck cannot tell you why the memory leaked, unfortunately. (Ignore =
the
+"vg_replace_malloc.c", that's an implementation detail.)</p>
+<p>There are several kinds of leaks; the two most important categories =
are:
=20
+</p>
+<div class=3D"itemizedlist"><ul type=3D"disc">
+<li><p>"definitely lost": your program is leaking memory -- fix
+ it!</p></li>
+<li><p>"probably lost": your program is leaking memory, unless
+ you're doing funny things with pointers (such as moving them to point=
to
+ the middle of a heap block).</p></li>
+</ul></div>
+<p>
=20
-<p>There are several kinds of leaks; the two most important
-categories are:</p>
-<ul>
- <li>"definitely lost": your program is leaking memory -- fix it!</li>
-
- <li>"probably lost": your program is leaking memory, unless
- you're doing funny things with pointers (such as moving them
- to point to the middle of a heap block).</li>
-</ul>
-
-<p>If you don't understand an error message, please consult
-section 3 of the User Manual which has examples of all the error
-messages Memcheck produces.</p>
-
-
-<h3>4. Caveats.</h3>
-
-<p>Memcheck is not perfect; it occasionally produces false
-positives, and there are mechanisms for suppressing these (see
-"suppressions" in the User Manual). However, it is typically
-right 99% of the time, so you should be wary of ignoring its
-error messages. After all, you wouldn't ignore warning messages
-produced by a compiler, right?</p>
-
-<p>Memcheck also cannot detect every memory error your program
-has. For example, it can't detect if you overrun the bounds of
-an array that is allocated statically or on the stack.</p>
-
-
-
-<h3>5. More information.</h3>
-
-<p>Please consult the FAQ and the User Manual, which have much
-more information. Note that the other tools in the Valgrind
-distribution can be invoked with the <code>--tool</code>
-option.</p>
-
+If you don't understand an error message, please consult
+<a href=3D"mc-manual.html#mc-manual.errormsgs">Explanation of error mess=
ages from Memcheck</a> in the <a href=3D"manual.html">Valgrind User Manua=
l</a> which has
+examples of all the error messages Memcheck produces.</p>
+</div>
+<div class=3D"sect1" lang=3D"en">
+<div class=3D"titlepage">
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"quick-start.caveats"></a>4.=A0Caveats</h2></div></div>
+<div></div>
+</div>
+<p>Memcheck is not perfect; it occasionally produces false positives,
+and there are mechanisms for suppressing these (see
+<a href=3D"manual-core.html#manual-core.suppress">Suppressing errors</a>=
in the <a href=3D"manual.html">Valgrind User Manual</a>).
+However, it is typically right 99% of the time, so you should be wary of
+ignoring its error messages. After all, you wouldn't ignore warning
+messages produced by a compiler, right?</p>
+<p>Memcheck also cannot detect every memory error your program has. For
+example, it can't detect if you overrun the bounds of an array that is
+allocated statically or on the stack.</p>
+</div>
+<div class=3D"sect1" lang=3D"en">
+<div class=3D"titlepage">
+<div><div><h2 class=3D"title" style=3D"clear: both">
+<a name=3D"quick-start.info"></a>5.=A0More information</h2></div></div>
+<div></div>
+</div>
+<p>Please consult the <a href=3D"FAQ.html">Valgrind FAQ</a> and the
+<a href=3D"manual.html">Valgrind User Manual</a>, which have much more i=
nformation. Note that the
+other tools in the Valgrind distribution can be invoked with the
+<tt class=3D"computeroutput">--tool</tt> option.</p>
+</div>
+</div>
+<div>
+<br><table class=3D"nav" width=3D"100%" cellspacing=3D"3" cellpadding=3D=
"2" border=3D"0" summary=3D"Navigation footer">
+<tr>
+<td rowspan=3D"2" width=3D"40%" align=3D"left">
+<a accesskey=3D"p" href=3D"index.html"><<=A0Valgrind Documentation=
</a>=A0</td>
+<td width=3D"20%" align=3D"center"><a accesskey=3D"u" href=3D"index.html=
">Up</a></td>
+<td rowspan=3D"2" width=3D"40%" align=3D"right">=A0<a accesskey=3D"n" hr=
ef=3D"manual.html">Valgrind User Manual=A0>></a>
+</td>
+</tr>
+<tr><td width=3D"20%" align=3D"center"><a accesskey=3D"h" href=3D"index.=
html">Home</a></td></tr>
+</table>
+</div>
|
|
From: <sv...@va...> - 2005-08-03 22:39:45
|
Author: de Date: 2005-08-03 23:39:44 +0100 (Wed, 03 Aug 2005) New Revision: 158 Log: - removed references to "developer release" as is pointless; developers can get current dev. release from svn anytime and rm'd refs to "stable release". Now we just have "Release X.X.X" - added blurb re 3.0.0 release Modified: trunk/downloads/source_code.html Modified: trunk/downloads/source_code.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/source_code.html 2005-08-03 22:39:23 UTC (rev 157) +++ trunk/downloads/source_code.html 2005-08-03 22:39:44 UTC (rev 158) @@ -2,8 +2,8 @@ =20 =20 <p>The complete source code, including documentation, is -available as a tarball for the current stable and developer -releases. For downloadable / browseable manual packages, go to +available as a tarball for the current releases. =20 +For downloadable / browseable manual packages, go to the <a href=3D"/docs/download_docs.html">Documentation</a> page. For older releases, see the=20 <a href=3D"/downloads/archive.html">Release Archive</a> page.</p> @@ -17,14 +17,40 @@ =20 <div class=3D"hr_brown"><hr/></div> =20 - <div id=3D"release"> =20 -<a name=3D"current-stable"></a> -<h3>Current Stable Release:</h3> +<a name=3D"current"></a> =20 -<p> -<a href=3D"/downloads/valgrind-2.4.1.tar.bz2">valgrind 2.4.1 (tar.bz2)</= a>=20 +<h3>Release 3.0.0</h3> + +<p><a href=3D"/downloads/valgrind-3.0.0.tar.bz2">valgrind 3.0.0 (tar.bz2= )</a>=20 +[2679Kb] - 3 August 2005.<br /> +<span class=3D"md5sum">md5: e976a343c61d9505162f595a8aeb09c1</span></p> + +<p>3.0.0 is a major overhaul of Valgrind. There have been many changes +and improvements. The most significant user visible change is that +Valgrind now supports architectures other than x86. 3.0.0 supports +both X86 and AMD64 running Linux. PPC32 on Linux is under development +but not yet usable. See the NEWS file for details of these and many +other changes.</p> + +<p>3.0.0 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>amd64 running SuSE 9.2, Fedora Core 2, 3 and 4</li> + <li>x86 running SuSE 9.1, 9.2, 9.3, RedHat 7.3, Redhat 8, Fedora Core = 4</li> +</ul> + +<p>We believe it should work on Linux distributions with kernel 2.4 or +2.6 and glibc 2.2.X or 2.3.X.</p> + + + + +<h3>Release 2.4.1</h3> + +<p><a href=3D"/downloads/valgrind-2.4.1.tar.bz2">valgrind 2.4.1 (tar.bz2= )</a>=20 [1078Kb] - 1 August 2005. For x86-linux only.<br /> <span class=3D"md5sum">md5: 8ada0f37ddd940032b85ea859fedb037</span> </p> @@ -38,20 +64,12 @@ Core 4, SuSE 9.1 and 9.3. We believe it should work on Linux distributions with kernel 2.4 or 2.6 and glibc 2.2.X or 2.3.X.</p> =20 +</div> =20 =20 -<a name=3D"current-devel"></a> -<h3>Current Developer Release: </h3> =20 -<p>2.4.1 supersedes all previous releases, and so there is -currently no development release available.</p> - - -</div> - <div class=3D"hr_brown"><hr/></div> =20 - <h3>RPMs / Binaries</h3> =20 <p>We do not distribute binaries or RPMs. The releases available @@ -70,4 +88,3 @@ the Memcheck tool. Therefore, it's best to use Valgrind on the most capable machine you can get your hands on. </p> - |
|
From: <sv...@va...> - 2005-08-03 22:39:26
|
Author: de
Date: 2005-08-03 23:39:23 +0100 (Wed, 03 Aug 2005)
New Revision: 157
Log:
- changed target name from 'current-stable' to 'current'
Modified:
trunk/devel/platforms.html
Modified: trunk/devel/platforms.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/devel/platforms.html 2005-08-03 22:38:46 UTC (rev 156)
+++ trunk/devel/platforms.html 2005-08-03 22:39:23 UTC (rev 157)
@@ -50,7 +50,7 @@
<p>For details of which distributions the current release
(<?php echo $config['release-version']; ?>) builds
and runs its regression tests on, see the=20
- <a href=3D"/downloads/source_code.html#current-stable">release
+ <a href=3D"/downloads/source_code.html#current">release
notes</a>.</p>
</dd>
=20
|
|
From: <sv...@va...> - 2005-08-03 22:38:47
|
Author: de Date: 2005-08-03 23:38:46 +0100 (Wed, 03 Aug 2005) New Revision: 156 Log: - added 3.0.0 release to news list Modified: trunk/info/news.html Modified: trunk/info/news.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/info/news.html 2005-08-03 22:38:02 UTC (rev 155) +++ trunk/info/news.html 2005-08-03 22:38:46 UTC (rev 156) @@ -7,11 +7,15 @@ =20 <ul> =20 - <li><p>1 August 2005: A new stable version, 2.4.1, is + <li><p>August 3 2005: A new stable version, 3.0.0 is available. + 3.0.0 is a major new release, with support for both x86-linux and=20 + amd64-linux, and many other improvements.</p></li> + + <li><p>August 1 2005: A new stable version, 2.4.1, is available.</p></li> =20 <li><p>March 24, 2005:<br /> A new stable release,=20 - <a href=3D"/downloads/source_code.html#current-stable">valgrind + <a href=3D"/downloads/source_code.html#current">valgrind 2.4.0</a>, is available. Relative to 2.2.0, 2.4.0 has improved thread and signal support, reduced memory consumption, and dozens of bug fixes.</p></li> @@ -26,7 +30,7 @@ </p></li> =20 <li><p>August 31, 2004:<br /> A new stable release,=20 - <a href=3D"/downloads/source_code.html#current-stable">valgrind + <a href=3D"/downloads/source_code.html#current">valgrind 2.2.0</a>, is available. 2.2.0 brings many improvements over 2.0.0, and includes the new Massif heap-profiling tool.</p></li> =20 |
|
From: <sv...@va...> - 2005-08-03 22:38:07
|
Author: de
Date: 2005-08-03 23:38:02 +0100 (Wed, 03 Aug 2005)
New Revision: 155
Log:
/php/header.php
- changed meta text version number
/php/.htconfx
- updated release-date and release-version
Modified:
trunk/php/.htconfx
trunk/php/header.php
Modified: trunk/php/.htconfx
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/php/.htconfx 2005-08-03 22:37:01 UTC (rev 154)
+++ trunk/php/.htconfx 2005-08-03 22:38:02 UTC (rev 155)
@@ -27,8 +27,8 @@
'dt_copyright' =3D> '2000-2005 ',
=20
/* current release info */
- 'release-date' =3D> '1 August 2005',
- 'release-version' =3D> 'valgrind-2.4.1',
+ 'release-date' =3D> '3 August 2005',
+ 'release-version' =3D> 'valgrind-3.0.0',
=20
/* mailing lists, bug reports, etc. */
'vgannounce' =3D> array(=20
Modified: trunk/php/header.php
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/php/header.php 2005-08-03 22:37:01 UTC (rev 154)
+++ trunk/php/header.php 2005-08-03 22:38:02 UTC (rev 155)
@@ -19,10 +19,10 @@
<style type=3D"text/css">@import url('/css/valgrind.css');</style>
<link rel=3D"shortcut icon" href=3D"/favicon.ico" />
<link rel=3D"icon" href=3D"/favicon.ico" type=3D"image/x-icon" />
- <meta name=3D"description" content=3D"Official Home Page for valgrind, =
a suite of tools for debugging and profiling. Automatically detect memory=
management and threading bugs, and perform detailed profiling. The curr=
ent stable version is valgrind 2.4.0."/>
+ <meta name=3D"description" content=3D"Official Home Page for valgrind, =
a suite of tools for debugging and profiling. Automatically detect memory=
management and threading bugs, and perform detailed profiling. The curr=
ent stable version is valgrind 3.0.0."/>
<meta name=3D"keywords" content=3D"Valgrind Memcheck Addrcheck Cachegri=
nd Massif Helgrind memory-management uninitialised memory memory leaks pa=
ssing uninitialised memory overlapping pointers misuses of the POSIX pthr=
eads"/>
</head>
-=20
+
<!-- dont we all just wish IE && Netscape 4.x to /dev/null -->
<body topmargin=3D"0" leftmargin=3D"0" marginwidth=3D"0" marginheight=3D=
"0"=20
bgcolor=3D"#ffffff" text=3D"#202020"=20
|
|
From: <sv...@va...> - 2005-08-03 22:37:05
|
Author: de Date: 2005-08-03 23:37:01 +0100 (Wed, 03 Aug 2005) New Revision: 154 Log: - changed 'Current stable release' to 'Current release' - added v.3 blurb to 'Recent News' Modified: trunk/index.html Modified: trunk/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/index.html 2005-08-03 18:06:37 UTC (rev 153) +++ trunk/index.html 2005-08-03 22:37:01 UTC (rev 154) @@ -6,7 +6,7 @@ =20 =20 <h3 align=3D"center"> -Current stable release: <a href=3D"/downloads/source_code.html#current-s= table"><?php echo $config['release-version']; ?></a> +Current release: <a href=3D"/downloads/source_code.html#current"><?php e= cho $config['release-version']; ?></a> </h3> =20 <p> </p> @@ -37,7 +37,10 @@ =20 <ul> =20 - <li><p>1 August 2005: A new stable version, 2.4.1, is + <li><p>August 3 2005: Valgrind 3.0.0, for x86-linux and amd64-linux,=20 + is available.</p></li> + + <li><p>August 1 2005: A new stable version, 2.4.1, is available.</p></li> =20 <li><p>March 12, 2005: The Valgrind website has been overhauled, |
|
From: <sv...@va...> - 2005-08-03 20:42:14
|
Author: sewardj Date: 2005-08-03 21:42:06 +0100 (Wed, 03 Aug 2005) New Revision: 4316 Log: 3.0.0 second try, sigh. Modified: trunk/ACKNOWLEDGEMENTS trunk/NEWS Modified: trunk/ACKNOWLEDGEMENTS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/ACKNOWLEDGEMENTS 2005-08-03 20:28:33 UTC (rev 4315) +++ trunk/ACKNOWLEDGEMENTS 2005-08-03 20:42:06 UTC (rev 4316) @@ -1,4 +1,9 @@ =20 +Cerion Armour-Brown, ce...@op... + +Cerion worked on PowerPC instruction set support using the Vex +dynamic-translation framework. + Jeremy Fitzhardinge, je...@va... =20 Jeremy wrote Helgrind and totally overhauled low-level syscall/signal Modified: trunk/NEWS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/NEWS 2005-08-03 20:28:33 UTC (rev 4315) +++ trunk/NEWS 2005-08-03 20:42:06 UTC (rev 4316) @@ -150,7 +150,7 @@ 75247 x86_64/amd64 support (the biggest "bug" we have ever fixed) =20 (3.0RC1: 27 July 05, vex r1303, valgrind r4283). -(3.0.0: 3 August 05, vex r1313, valgrind r4313). +(3.0.0: 3 August 05, vex r1313, valgrind r4316). =20 =20 =20 |
|
From: <sv...@va...> - 2005-08-03 20:28:38
|
Author: de Date: 2005-08-03 21:28:33 +0100 (Wed, 03 Aug 2005) New Revision: 4315 Log: Minor tweaks to get the FAQ on one page, per nick's request Modified: trunk/docs/xml/FAQ.xml trunk/docs/xml/vg-entities.xml Modified: trunk/docs/xml/FAQ.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/xml/FAQ.xml 2005-08-03 18:58:45 UTC (rev 4314) +++ trunk/docs/xml/FAQ.xml 2005-08-03 20:28:33 UTC (rev 4315) @@ -4,13 +4,21 @@ [ <!ENTITY % vg-entities SYSTEM "vg-entities.xml"> %vg-entities; ]> =20 <book id=3D"FAQ" xreflabel=3D"Valgrind FAQ"> +<title>Valgrind FAQ</title> +<bookinfo> + <subtitle>Valgrind Frequently Asked Questions</subtitle> + <releaseinfo>August 2005</releaseinfo> + <author> + <surname> + <ulink url=3D"http://www.valgrind.org/www/developers.html">Valgrin= d Developers</ulink> + </surname> + <affiliation><orgname> + <ulink url=3D"mailto:&vg-vemail;">&vg-vemail;</ulink> + </orgname></affiliation> + </author> +</bookinfo> =20 - <bookinfo> - <title>Valgrind FAQ</title> - </bookinfo> - - -<chapter id=3D"faq.background" xreflabel=3D"Background"> +<sect1 id=3D"faq.background" xreflabel=3D"Background"> <title>Background</title> =20 <qandaset id=3D"qset.background"> @@ -53,10 +61,10 @@ =20 </qandaset> =20 -</chapter> +</sect1> =20 =20 -<chapter id=3D"faq.installing"=20 +<sect1 id=3D"faq.installing"=20 xreflabel=3D"Compiling, installing and configuring"> <title>Compiling, installing and configuring</title> <qandaset id=3D"qset.installing"> @@ -82,11 +90,11 @@ </qandaentry> =20 </qandaset> -</chapter> +</sect1> =20 =20 =20 -<chapter id=3D"faq.abort"=20 +<sect1 id=3D"faq.abort"=20 xreflabel=3D"Valgrind aborts unexpectedly"> <title>Valgrind aborts unexpectedly</title> <qandaset id=3D"qset.abort"> @@ -174,10 +182,10 @@ </qandaentry> =20 </qandaset> -</chapter> +</sect1> =20 =20 -<chapter id=3D"faq.unexpected"=20 +<sect1 id=3D"faq.unexpected"=20 xreflabel=3D"Valgrind behaves unexpectedly"> <title>Valgrind behaves unexpectedly</title> <qandaset id=3D"qset.unexpected"> @@ -359,10 +367,10 @@ </qandaentry> =20 </qandaset> -</chapter> +</sect1> =20 =20 -<chapter id=3D"faq.notfound" xreflabel=3D"Memcheck doesn't find my bug"> +<sect1 id=3D"faq.notfound" xreflabel=3D"Memcheck doesn't find my bug"> <title>Memcheck doesn't find my bug</title> <qandaset id=3D"qset.notfound"> =20 @@ -438,10 +446,10 @@ =20 =20 </qandaset> -</chapter> +</sect1> =20 =20 -<chapter id=3D"faq.misc"=20 +<sect1 id=3D"faq.misc"=20 xreflabel=3D"Miscellaneous"> <title>Miscellaneous</title> <qandaset id=3D"qset.misc"> @@ -505,11 +513,11 @@ =20 =20 </qandaset> -</chapter> +</sect1> =20 =20 <!-- template=20 -<chapter id=3D"faq."=20 +<sect1 id=3D"faq."=20 xreflabel=3D"xx"> <title>xx</title> <qandaset id=3D"qset."> @@ -524,12 +532,12 @@ </qandaentry> =20 </qandaset> -</chapter> +</sect1> --> =20 =20 =20 -<chapter id=3D"faq.help" xreflabel=3D"How To Get Further Assistance"> +<sect1 id=3D"faq.help" xreflabel=3D"How To Get Further Assistance"> <title>How To Get Further Assistance</title> =20 =20 @@ -572,6 +580,7 @@ you are probably requesting help from unpaid volunteers, so you have no guarantee of receiving an answer.</para> =20 -</chapter> +</sect1> =20 + </book> Modified: trunk/docs/xml/vg-entities.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/xml/vg-entities.xml 2005-08-03 18:58:45 UTC (rev 4314) +++ trunk/docs/xml/vg-entities.xml 2005-08-03 20:28:33 UTC (rev 4315) @@ -8,5 +8,5 @@ <!-- valgrind release + version stuff --> <!ENTITY rel-type "Release"> <!ENTITY rel-version "3.0.0"> -<!ENTITY rel-date "July 24 2005"> +<!ENTITY rel-date "August 3 2005"> =20 |
|
From: Oswald B. <os...@kd...> - 2005-08-03 19:18:31
|
On Wed, Aug 03, 2005 at 07:52:45AM -0700, Paul Pluzhnikov wrote: > *** vgtest_ume.stderr.exp 2005-07-02 15:43:03.000000000 -0700 > --- vgtest_ume.stderr.out 2005-08-03 07:41:05.000000000 -0700 > *************** > *** 4 **** > ! Hello, world! > --- 4,5 ---- > ! Warning: client syscall mmap2 tried to modify addresses 0x........-0x........ > ! valgrind: mmap(0x........, 4096) failed in UME. > how about changing to unified diffs? this context diff crap is hardly readable and certainly not meant for humans ... just an idea ... it probably makes sense to use a relatively big amount of context for the patches to avoid creating many chunks. or maybe not. :) -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. |
|
From: <sv...@va...> - 2005-08-03 18:58:49
|
Author: de Date: 2005-08-03 19:58:45 +0100 (Wed, 03 Aug 2005) New Revision: 4314 Log: minor tweaks Modified: trunk/docs/internals/xml-output.txt trunk/docs/lib/vg-common.xsl Modified: trunk/docs/internals/xml-output.txt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/internals/xml-output.txt 2005-08-03 17:01:51 UTC (rev 4313= ) +++ trunk/docs/internals/xml-output.txt 2005-08-03 18:58:45 UTC (rev 4314= ) @@ -30,7 +30,7 @@ How to use ~~~~~~~~~~ =20 -Run with flag --xml=3Dyes. That's all. Note however several=20 +Run with flag --xml=3Dyes. That`s all. Note however several=20 caveats. =20 * At the present time only Memcheck is supported. The scheme extends @@ -98,7 +98,7 @@ Inside that, the first entity is an indication of the protocol version. This is provided so that existing parsers can identify XML created by future versions of Valgrind merely by observing that the -protocol version is one they don't understand. Hence TOPLEVEL is: +protocol version is one they don`t understand. Hence TOPLEVEL is: =20 <?xml version=3D"1.0"?> <valgrindoutput> @@ -184,7 +184,7 @@ * Zero or more ERRORs, each of which is a complaint from the leak checker. =20 -That's it. +That`s it. =20 =20 ERROR Modified: trunk/docs/lib/vg-common.xsl =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/lib/vg-common.xsl 2005-08-03 17:01:51 UTC (rev 4313) +++ trunk/docs/lib/vg-common.xsl 2005-08-03 18:58:45 UTC (rev 4314) @@ -16,7 +16,7 @@ </l:l10n> </l:i18n> =20 -<!-- don't generate sub-tocs for qanda sets --> +<!-- do not generate sub-tocs for qanda sets --> <xsl:param name=3D"generate.toc"> set toc,title book toc,title,figure,table,example,equation |
|
From: <sv...@va...> - 2005-08-03 18:06:43
|
Author: de Date: 2005-08-03 19:06:37 +0100 (Wed, 03 Aug 2005) New Revision: 153 Log: /docs/mini-tut.html - deleted as unwanted /docs/bookset/ - deleted old v.2.1.1 of manual Removed: trunk/docs/bookset/ trunk/docs/mini-tut.html Deleted: trunk/docs/mini-tut.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/mini-tut.html 2005-08-03 18:02:48 UTC (rev 152) +++ trunk/docs/mini-tut.html 2005-08-03 18:06:37 UTC (rev 153) @@ -1,70 +0,0 @@ -<h1>Mini-Tutorial</h1> - -<h4>Courtesy of=20 -<a href=3D"http://www.cs.swarthmore.edu/~newhall/">Dr Tia Newhall</a></h= 4> -<?php -/* http://www.cs.swarthmore.edu/~newhall/unixhelp/purify.html */ -?> - -<p>Valgrind is a tool for finding memory access errors in your -code (memory leaks, reading uninitialized memory, accessing -unallocated memory, array out-of-bounds errors, ...). For C and -C++ programs, memory access errors are the most difficult bugs to -find and to fix. These tools can save you days worth of debugging -time by quickly pointing you to the source and type of memory -access errors in your code, so that you can easily determine what -to fix and how to fix it.</p> - -<p>In /home/newhall/public/purify_valgrind_examples/ is an -example program with bad memory access errors that you can use to -try out valgrind. Included are sample Makefiles for building -executables on Linux. The README file gives simple instructions -for using valgrind. More detailed instructions are listed -below:</p> - -<p>Running valgrind is easy. Just compile your program with -g, then -run the executable (for non-interactive programs, you will likely -want to re-direct output to a file since valgrind can generate a -lot of output):</p> -<pre class=3D"programlisting"> -% valgrind -v ./a.out=20 -% valgrind -v ./a.out >& out # re-direct valgrind (and a.out) output t= o file 'out' -</pre> - -<p>If you look through the out file, you may see memory errors -listed like this:</p> -<pre class=3D"programlisting"> -=3D=3D9860=3D=3D Invalid write of size 1 -=3D=3D9860=3D=3D at 0x8048532: foo (main.c:28) -=3D=3D9860=3D=3D by 0x804859F: main (main.c:48) -=3D=3D9860=3D=3D by 0x4023514E: __libc_start_main (in /lib/libc-2.2.5= .so) -=3D=3D9860=3D=3D by 0x80483D0: (within ~/newhall/public/purify_exampl= es/badprog) -=3D=3D9860=3D=3D Address 0x40F33061 is 0 bytes after a block of size = 5 alloc'd -=3D=3D9860=3D=3D at 0x401678B8: malloc (vg_clientfuncs.c:103) -=3D=3D9860=3D=3D by 0x80484C8: foo (main.c:17) -=3D=3D9860=3D=3D by 0x804859F: main (main.c:48) -=3D=3D9860=3D=3D by 0x4023514E: __libc_start_main (in /lib/libc-2.2.5= .so) -</pre> - -<p>This tells me that in function foo, at line 28 in main.c, my -program is writing 1 byte beyond the array that was allocated at -line 17 in function foo (9860 was the process ID of my running -program). If I look at lines 17 and 28 of my program, the error -is obvious (my loop executes one to many times, accessing c[5], -which is beyond the end of array c, on the last iteration):</p> - -<pre class=3D"programlisting"> -17 c =3D (char *)malloc(sizeof(char)*5); -18 strcpy(c, "cccc"); -19=20 -... -27 for( i=3D0; i <=3D 5; i++ ) { -28 c[i] =3D str[i]; -29 } -</pre> - -<br /> -<p><b>Note:</b> See the "Usage" section of the=20 -<a href=3D"/docs/valgrind-HOWTO/">HOWTO</a> for more information on -using valgrind.</p> - |
|
From: <sv...@va...> - 2005-08-03 18:02:53
|
Author: de Date: 2005-08-03 19:02:48 +0100 (Wed, 03 Aug 2005) New Revision: 152 Log: - deleted /docs/HOWTO as unwanted Removed: trunk/docs/HOWTO/ |
|
From: Tom H. <to...@co...> - 2005-08-03 17:47:20
|
In message <200...@ja...>
sv...@va... wrote:
> + Bugzilla. It's unclear how to do this consistently. The approach
> + taken for 3.0.0 was to go to this page in KDE's bugzilla:
> + http://bugs.kde.org/query.cgi
> + and to create a search where
> + "Status and severity" / Status field is set to RESOLVED
> + and
> + "Involved People" / Email, bug-owner contains "jseward"
> + since I believe js...@ac... is the owner of all bugs.
> + This creates a long list of bugs which does not conveniently stop
> + at the previous release. Work backwards through this list until
> + either (1) you run out of patience, or (2) most of the bugs seem
> + to pertain to previous releases and are now irrelevant. In short
> + this is not a very scientific or robust way to collect up all
> + bugs fixed since last time.
They are all owned by you to start with, but they do sometimes get
transferred to other people. Setting product to "valgrind" should
be a better method.
You could probably also filter on the change date of the resolution
and/or status fields to narrow things down a bit more.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: <sv...@va...> - 2005-08-03 17:01:56
|
Author: sewardj Date: 2005-08-03 18:01:51 +0100 (Wed, 03 Aug 2005) New Revision: 4313 Log: Hopefully this is the final commit for 3.0.0. Modified: trunk/NEWS trunk/configure.in trunk/docs/internals/release-HOWTO Modified: trunk/NEWS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/NEWS 2005-08-03 16:40:10 UTC (rev 4312) +++ trunk/NEWS 2005-08-03 17:01:51 UTC (rev 4313) @@ -149,7 +149,8 @@ 101543 Support fadvise64 syscalls 75247 x86_64/amd64 support (the biggest "bug" we have ever fixed) =20 -(3.0RC1: 27 July 05, vex r1303, valgrind r4283). +(3.0RC1: 27 July 05, vex r1303, valgrind r4283). +(3.0.0: 3 August 05, vex r1313, valgrind r4313). =20 =20 =20 Modified: trunk/configure.in =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/configure.in 2005-08-03 16:40:10 UTC (rev 4312) +++ trunk/configure.in 2005-08-03 17:01:51 UTC (rev 4313) @@ -1,5 +1,5 @@ # Process this file with autoconf to produce a configure script. -AC_INIT(Valgrind, 3.0.RC1, val...@li...) +AC_INIT(Valgrind, 3.0.0, val...@li...) AC_CONFIG_SRCDIR(coregrind/m_main.c) AM_CONFIG_HEADER(config.h) AM_INIT_AUTOMAKE Modified: trunk/docs/internals/release-HOWTO =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/internals/release-HOWTO 2005-08-03 16:40:10 UTC (rev 4312) +++ trunk/docs/internals/release-HOWTO 2005-08-03 17:01:51 UTC (rev 4313) @@ -15,8 +15,20 @@ of tasks for the official release.) =20 - Write release notes, add to NEWS. Include a list of fixed bugs from - Bugzilla. [[We should decide a defined way of obtaining this list so = it's - consistent and so we don't have to work it out anew each time.]] + Bugzilla. It's unclear how to do this consistently. The approach + taken for 3.0.0 was to go to this page in KDE's bugzilla: + http://bugs.kde.org/query.cgi + and to create a search where + "Status and severity" / Status field is set to RESOLVED + and + "Involved People" / Email, bug-owner contains "jseward" + since I believe js...@ac... is the owner of all bugs. + This creates a long list of bugs which does not conveniently stop=20 + at the previous release. Work backwards through this list until + either (1) you run out of patience, or (2) most of the bugs seem + to pertain to previous releases and are now irrelevant. In short + this is not a very scientific or robust way to collect up all + bugs fixed since last time. =20 - Other files that might need updating: README, README_DEVELOPERS, README_PACKAGERS. |
|
From: Julian S. <js...@ac...> - 2005-08-03 17:00:38
|
Hi. I'm rolling the 3.0.0 tarball pretty much now, branching/tagging, testing the tarball, etc. That should keep me busy for a few hours. So pls don't commit anything more now. Obviously I'll mail again when done. J |
|
From: <sv...@va...> - 2005-08-03 16:40:12
|
Author: sewardj Date: 2005-08-03 17:40:10 +0100 (Wed, 03 Aug 2005) New Revision: 4312 Log: Almost-final wibbles. Modified: trunk/NEWS Modified: trunk/NEWS =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/NEWS 2005-08-03 16:39:44 UTC (rev 4311) +++ trunk/NEWS 2005-08-03 16:40:10 UTC (rev 4312) @@ -110,7 +110,8 @@ =20 BUGS FIXED: =20 -199810 vex amd64->IR: unhandled instruction bytes: 0xA3 0x4C 0x70 0xD7 +110046 sz =3D=3D 4 assertion failed=20 +109810 vex amd64->IR: unhandled instruction bytes: 0xA3 0x4C 0x70 0xD7 109802 Add a plausible_stack_size command-line parameter ? 109783 unhandled ioctl TIOCMGET (running hw detection tool discover)=20 109780 unhandled ioctl BLKSSZGET (running fdisk -l /dev/hda) |
|
From: <sv...@va...> - 2005-08-03 16:39:47
|
Author: sewardj Date: 2005-08-03 17:39:44 +0100 (Wed, 03 Aug 2005) New Revision: 4311 Log: Copy the right stuff into the tarball. Modified: trunk/Makefile.am Modified: trunk/Makefile.am =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/Makefile.am 2005-08-03 16:39:08 UTC (rev 4310) +++ trunk/Makefile.am 2005-08-03 16:39:44 UTC (rev 4311) @@ -81,8 +81,9 @@ # These list the bits of vex we need to copy into the tarball =20 VEX_PRIMARY_SOURCES =3D \ - VEX/README \ - VEX/COPYING \ + VEX/HACKING.README \ + VEX/LICENSE.README \ + VEX/LICENSE.GPL \ VEX/Makefile \ VEX/auxprogs/genoffsets.c \ VEX/pub/libvex_guest_amd64.h \ |
|
From: <sv...@va...> - 2005-08-03 16:39:10
|
Author: sewardj
Date: 2005-08-03 17:39:08 +0100 (Wed, 03 Aug 2005)
New Revision: 4310
Log:
Do per-chapter chunking for the html output.
Modified:
trunk/docs/lib/vg-html-chunk.xsl
Modified: trunk/docs/lib/vg-html-chunk.xsl
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/lib/vg-html-chunk.xsl 2005-08-02 23:07:02 UTC (rev 4309)
+++ trunk/docs/lib/vg-html-chunk.xsl 2005-08-03 16:39:08 UTC (rev 4310)
@@ -15,6 +15,8 @@
<xsl:param name=3D"chunker.output.indent" select=3D"'yes'"/>
<!-- use our custom html stylesheet -->
<xsl:param name=3D"html.stylesheet" select=3D"'vg_basic.css'"/>
+<!-- set chunking at the chapter level only -->
+<xsl:param name=3D"chunk.section.depth" select=3D"'0'"/>=20
=20
<!-- use our custom header -->
<xsl:template name=3D"header.navigation">
@@ -104,7 +106,7 @@
<xsl:apply-templates select=3D"$up" mode=3D"object.title.markup"=
/>
</xsl:when>
<xsl:otherwise>
- <xsl:text>Valgrind User's Manual</xsl:text>
+ <xsl:text>Valgrind User`s Manual</xsl:text>
</xsl:otherwise>
</xsl:choose>
-->
@@ -151,11 +153,9 @@
or count($next) > 0"/>
=20
<xsl:variable name=3D"row2" select=3D"($prev !=3D 0)
- or (generate-id($home) !=3D generate=
-id(.)
- or $nav.context =3D 'toc')
- or ($chunk.tocs.and.lots !=3D 0
- and $nav.context !=3D 'toc')
- or ($next !=3D 0)"/>
+ or (generate-id($home) !=3D generate-id(.) or $nav.context =
=3D 'toc')
+ or ($chunk.tocs.and.lots !=3D 0 and $nav.context !=3D 'toc'=
)
+ or ($next !=3D 0)"/>
<div>
<xsl:if test=3D"$row1 or $row2">
<br />
@@ -251,7 +251,7 @@
</div>
</xsl:template>
=20
-<!-- We don't like tables with borders -->
+<!-- We don`t like tables with borders -->
<xsl:template match=3D"revhistory" mode=3D"titlepage.mode">
<xsl:variable name=3D"numcols">
<xsl:choose>
@@ -271,7 +271,7 @@
</table>
</xsl:template>
=20
-<!-- don't put an expanded set-level TOC, only book titles -->
+<!-- don`t put an expanded set-level TOC, only book titles -->
<xsl:template match=3D"book" mode=3D"toc">
<xsl:param name=3D"toc-context" select=3D"."/>
<xsl:choose>
|
Author: sewardj Date: 2005-08-03 17:07:36 +0100 (Wed, 03 Aug 2005) New Revision: 1313 Log: Implement dual licensing. Added: trunk/HACKING.README trunk/LICENSE.GPL trunk/LICENSE.README Removed: trunk/COPYING trunk/README Modified: trunk/auxprogs/genoffsets.c trunk/priv/guest-amd64/gdefs.h trunk/priv/guest-amd64/ghelpers.c trunk/priv/guest-amd64/toIR.c trunk/priv/guest-arm/gdefs.h trunk/priv/guest-arm/ghelpers.c trunk/priv/guest-arm/toIR.c trunk/priv/guest-generic/bb_to_IR.c trunk/priv/guest-generic/bb_to_IR.h trunk/priv/guest-generic/g_generic_x87.c trunk/priv/guest-generic/g_generic_x87.h trunk/priv/guest-ppc32/gdefs.h trunk/priv/guest-ppc32/ghelpers.c trunk/priv/guest-ppc32/toIR.c trunk/priv/guest-x86/gdefs.h trunk/priv/guest-x86/ghelpers.c trunk/priv/guest-x86/toIR.c trunk/priv/host-amd64/hdefs.c trunk/priv/host-amd64/hdefs.h trunk/priv/host-amd64/isel.c trunk/priv/host-arm/hdefs.c trunk/priv/host-arm/hdefs.h trunk/priv/host-arm/isel.c trunk/priv/host-generic/h_generic_regs.c trunk/priv/host-generic/h_generic_regs.h trunk/priv/host-generic/h_generic_simd64.c trunk/priv/host-generic/h_generic_simd64.h trunk/priv/host-generic/reg_alloc2.c trunk/priv/host-ppc32/hdefs.c trunk/priv/host-ppc32/hdefs.h trunk/priv/host-ppc32/isel.c trunk/priv/host-x86/hdefs.c trunk/priv/host-x86/hdefs.h trunk/priv/host-x86/isel.c trunk/priv/ir/irdefs.c trunk/priv/ir/irmatch.c trunk/priv/ir/irmatch.h trunk/priv/ir/iropt.c trunk/priv/ir/iropt.h trunk/priv/main/vex_globals.c trunk/priv/main/vex_globals.h trunk/priv/main/vex_main.c trunk/priv/main/vex_util.c trunk/priv/main/vex_util.h trunk/pub/libvex.h trunk/pub/libvex_basictypes.h trunk/pub/libvex_emwarn.h trunk/pub/libvex_guest_amd64.h trunk/pub/libvex_guest_arm.h trunk/pub/libvex_guest_ppc32.h trunk/pub/libvex_guest_x86.h trunk/pub/libvex_ir.h trunk/pub/libvex_trc_values.h [... diff too large to include ...] |
|
From: <sv...@va...> - 2005-08-03 15:47:38
|
Author: sewardj
Date: 2005-08-03 16:47:33 +0100 (Wed, 03 Aug 2005)
New Revision: 1312
Log:
Newer version of GPLv2 text with newer FSF addresses, no other changes.
Modified:
trunk/COPYING
Modified: trunk/COPYING
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/COPYING 2005-08-02 21:27:25 UTC (rev 1311)
+++ trunk/COPYING 2005-08-03 15:47:33 UTC (rev 1312)
@@ -2,7 +2,7 @@
Version 2, June 1991
=20
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ 51 Franklin St, Fifth Floor, Boston, MA 02110-13=
01 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
=20
@@ -55,7 +55,7 @@
=20
The precise terms and conditions for copying, distribution and
modification follow.
-
+=0C
GNU GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
=20
@@ -110,7 +110,7 @@
License. (Exception: if the Program itself is interactive but
does not normally print such an announcement, your work based on
the Program is not required to print an announcement.)
-
+=0C
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Program,
and can be reasonably considered independent and separate works in
@@ -168,7 +168,7 @@
access to copy the source code from the same place counts as
distribution of the source code, even though third parties are not
compelled to copy the source along with the object code.
-
+=0C
4. You may not copy, modify, sublicense, or distribute the Program
except as expressly provided under this License. Any attempt
otherwise to copy, modify, sublicense or distribute the Program is
@@ -225,7 +225,7 @@
=20
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
-
+=0C
8. If the distribution and/or use of the Program is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Program under this License
@@ -278,7 +278,7 @@
POSSIBILITY OF SUCH DAMAGES.
=20
END OF TERMS AND CONDITIONS
-
+=0C
How to Apply These Terms to Your New Programs
=20
If you develop a new program, and you want it to be of the greatest
@@ -305,7 +305,7 @@
=20
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
- Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307=
USA
+ Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-130=
1 USA
=20
=20
Also add information on how to contact you by electronic and paper mail.
@@ -313,7 +313,7 @@
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
=20
- Gnomovision version 69, Copyright (C) year name of author
+ Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `sho=
w w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
|