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
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(31) |
2
(27) |
|
3
(25) |
4
(21) |
5
(21) |
6
(21) |
7
(32) |
8
(23) |
9
(15) |
|
10
(12) |
11
(9) |
12
(10) |
13
(10) |
14
(9) |
15
(7) |
16
(20) |
|
17
(14) |
18
(71) |
19
(67) |
20
(50) |
21
(25) |
22
(15) |
23
(37) |
|
24
(25) |
25
(41) |
26
(34) |
27
(57) |
28
(20) |
29
(30) |
30
(13) |
|
31
(18) |
|
|
|
|
|
|
|
From: <sv...@va...> - 2005-07-25 23:50:23
|
Author: sewardj
Date: 2005-07-26 00:50:22 +0100 (Tue, 26 Jul 2005)
New Revision: 4263
Log:
wibble++
Modified:
trunk/docs/internals/release-HOWTO
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-07-25 23:36:58 UTC (rev 4262)
+++ trunk/docs/internals/release-HOWTO 2005-07-25 23:50:22 UTC (rev 4263)
@@ -38,6 +38,11 @@
- Make the tarball ("make dist") and put it on the web somewhere (it doe=
sn't
have to be on valgrind.org if another site is easier).
=20
+- Ensure the tarball builds, runs, regtests on the platforms of interest=
.
+ However redundant this seems, sometimes it can be that a from-the-repo
+ build works whereas a from-the-tarball one doesn't, usually due to som=
e
+ trivial installation problem.
+
- Announce the release:
- Email valgrind-users and valgrind-developers (but not valgrind-annou=
nce). =20
- Make clear it's a release candidate. =20
@@ -62,9 +67,12 @@
=20
- Change release number in AC_INIT() in configure.in to "X.Y.Z".
=20
+- Make the tarball ("make dist").
+
+- Check tarball builds, installs, regtests on platforms of interest.
+ If not, fix and repeat until success.
+
- Tag the repository ("VALGRIND_X_Y_Z").
-
-- Make the tarball ("make dist").
=20
- Update website:=20
- Put the tarball up.
@@ -76,7 +84,8 @@
X.Y.Z is one more than the release just done.
=20
- Announce the release:
- - Email valgrind-users, valgrind-developers, and valgrind-announce. =20
+ - Email valgrind-users, valgrind-developers, and valgrind-announce.
+ - Email Linux Weekly News.
- Include the release notes in the email.
=20
-
+- Go on holiday.
|
|
From: <sv...@va...> - 2005-07-25 23:37:00
|
Author: sewardj Date: 2005-07-26 00:36:58 +0100 (Tue, 26 Jul 2005) New Revision: 4262 Log: In the final install, copy the documentation .pdf/.ps to files with a bit of a more sensible name. Modified: trunk/docs/Makefile.am Modified: trunk/docs/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/docs/Makefile.am 2005-07-25 23:30:24 UTC (rev 4261) +++ trunk/docs/Makefile.am 2005-07-25 23:36:58 UTC (rev 4262) @@ -101,11 +101,11 @@ ifeq ($(BUILD_ALL_DOCS),yes) if test -r index.pdf ; then \ mkdir -p $(DESTDIR)$(datadir)/doc/valgrind/; \ - cp index.pdf $(DESTDIR)$(datadir)/doc/valgrind/; \ + cp index.pdf $(DESTDIR)$(datadir)/doc/valgrind/valgrind_manual.pdf; \ fi if test -r index.ps ; then \ mkdir -p $(DESTDIR)$(datadir)/doc/valgrind/; \ - cp index.ps $(DESTDIR)$(datadir)/doc/valgrind/; \ + cp index.ps $(DESTDIR)$(datadir)/doc/valgrind/valgrind_manual.ps; \ fi endif =20 |
|
From: <sv...@va...> - 2005-07-25 23:30:28
|
Author: njn
Date: 2005-07-26 00:30:24 +0100 (Tue, 26 Jul 2005)
New Revision: 4261
Log:
fix breakage/wibbles
Modified:
trunk/cachegrind/docs/cg-manual.xml
trunk/memcheck/docs/mc-manual.xml
Modified: trunk/cachegrind/docs/cg-manual.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/cachegrind/docs/cg-manual.xml 2005-07-25 23:30:06 UTC (rev 4260=
)
+++ trunk/cachegrind/docs/cg-manual.xml 2005-07-25 23:30:24 UTC (rev 4261=
)
@@ -35,7 +35,7 @@
</listitem>
</itemizedlist>
=20
-<para>On a modern x86 machine, an L1 miss will typically cost
+<para>On a modern machine, an L1 miss will typically cost
around 10 cycles, and an L2 miss can cost as much as 200
cycles. Detailed cache profiling can be very useful for improving
the performance of your program.</para>
Modified: trunk/memcheck/docs/mc-manual.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/memcheck/docs/mc-manual.xml 2005-07-25 23:30:06 UTC (rev 4260)
+++ trunk/memcheck/docs/mc-manual.xml 2005-07-25 23:30:24 UTC (rev 4261)
@@ -61,9 +61,8 @@
=20
<itemizedlist id=3D"leakcheck">
<listitem>
- <para><computeroutput>--leak-check=3Dno</computeroutput>
- <para><computeroutput>--leak-check=3Dsummary</computeroutput>
- [default]</para>
+ <para><computeroutput>--leak-check=3Dno</computeroutput></para>
+ <para><computeroutput>--leak-check=3Dsummary</computeroutput> [defau=
lt]</para>
<para><computeroutput>--leak-check=3Dfull</computeroutput></para>
<para>When enabled, search for memory leaks when the client
program finishes. A memory leak means a malloc'd block,
|
|
From: <sv...@va...> - 2005-07-25 23:30:09
|
Author: njn Date: 2005-07-26 00:30:06 +0100 (Tue, 26 Jul 2005) New Revision: 4260 Log: wibble Modified: trunk/docs/internals/release-HOWTO 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-07-25 23:18:44 UTC (rev 4259) +++ trunk/docs/internals/release-HOWTO 2005-07-25 23:30:06 UTC (rev 4260) @@ -24,6 +24,7 @@ stable release, ensure that VG_CORE_INTERFACE_VERSION in include/pub_tool_tooliface.h has been increased since the last release= . =20 + For each release candidate (should do release candidates for big release= s, bug-fix-only releases might not need one): =20 @@ -67,6 +68,7 @@ =20 - Update website:=20 - Put the tarball up. + - Update the docs at www.valgrind.org/ (?) - Update www.valgrind.org/downloads/source_code.html. =20 - Add a news item to the front page and also to valgrind.org/info/news= .html. =20 |
|
From: <sv...@va...> - 2005-07-25 23:18:48
|
Author: njn
Date: 2005-07-26 00:18:44 +0100 (Tue, 26 Jul 2005)
New Revision: 4259
Log:
Clean up command-line args info in the manual and man page for 3.0.0
release. =20
Modified:
trunk/docs/valgrind.1
trunk/docs/xml/manual-core.xml
trunk/memcheck/docs/mc-manual.xml
Modified: trunk/docs/valgrind.1
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/valgrind.1 2005-07-25 23:18:04 UTC (rev 4258)
+++ trunk/docs/valgrind.1 2005-07-25 23:18:44 UTC (rev 4259)
@@ -1,7 +1,7 @@
.TH VALGRIND "1" "" ""
=20
.SH NAME
-\fBvalgrind \fP- a memory debugger for x86-linux
+\fBvalgrind \fP- a suite of tools for debugging and profiling programs
=20
.SH SYNOPSIS
.nf
@@ -11,8 +11,8 @@
.fi
=20
.SH DESCRIPTION
-\fBvalgrind\fP is a flexible program for debugging and profiling Linux-x=
86
-executables. It consists of a core, which provides a synthetic x86 CPU
+\fBvalgrind\fP is a flexible program for debugging and profiling Linux
+executables. It consists of a core, which provides a synthetic CPU
in software, and a series of "tools", each of which is a debugging or
profiling tool. The architecture is modular, so that new tools can be
created easily and without disturbing the existing structure.
@@ -125,17 +125,25 @@
default debugger is gdb. This option is a template that is expanded by
\fBvalgrind\fP at runtime. \fB%f\fP is replaced with the executable's
file name and \fB%p\fP is replaced by the process ID of the executable.
+
.TP
.B
+--demangle=3D<yes|no> [default: yes]
+Enable or disable automatic demangling (decoding) of C++ names. Enabled =
by
+default. When enabled, \fBvalgrind\fP will attempt to translate encoded
+C++ procedure names back to something approaching the original. The
+demangler handles symbols mangled by g++ versions 2.X and 3.X.
=20
+.TP
+.B
--error-limit=3D<yes|no> [default: yes]
When enabled, \fBvalgrind\fP stops reporting errors after 30000 in total=
,
or 300 different ones, have been seen. This is to stop the error trackin=
g
machinery from becoming a huge performance overhead in programs with
many errors.
+
.TP
.B
-
--gen-suppressions=3D<yes|no> [default: no]
When enabled, \fBvalgrind\fP will pause after every error shown and
print the line:
@@ -174,6 +182,12 @@
=20
.TP
.B
+--input-fd=3D<number> [default: 0, stdin]
+Specify the file descriptor to use for reading input from the user. This
+is used whenever \fBvalgrind\fP needs to prompt the user for a decision.
+
+.TP
+.B
--log-file=3D<filename>
Specifies that \fBvalgrind\fP should send all of its messages to the
specified file. In fact, the file name used is created by concatenating
@@ -182,6 +196,39 @@
=20
.TP
.B
+--log-file-exactly=3D<filename>
+Just like \fB--log-file\fB, but the ".pid" suffix is not added. If you
+trace multiple processes with Valgrind when using this option the log
+file may get all messed up.
+
+.TP
+.B
+--log-fd=3D<number> [default: 2, stderr]
+Specifies that \fBvalgrind\fP should send all of its messages to
+the specified file descriptor. The default, 2, is the standard error
+channel (stderr). Note that this may interfere with the client's own
+use of stderr.
+
+.TP
+.B
+--log-file-qualifier=3D<VAR>
+Specifies that \fBvalgrind\fB should send all of its messages to the
+file named by the environment variable \fB$VAR\fB. This is useful when
+running MPI programs.
+
+.TP
+.B
+--log-socket=3D<ip-address:port-number>
+Specifies that \fBvalgrind\fP should send all of its messages to the
+specified port at the specified IP address. The port may be omitted,
+in which case port 1500 is used. If a connection cannot be made to
+the specified socket, \fBvalgrind\fP falls back to writing output to
+the standard error (stderr). This option is intended to be used in
+conjunction with the \fBvalgrind-listener\fP program. For further detail=
s,
+see section 2.3 of the user manual.
+
+.TP
+.B
--num-callers=3D<number> [default=3D12]
By default, \fBvalgrind\fP shows 12 levels of function call names to
help you identify program locations. You can change that number with
@@ -206,12 +253,25 @@
=20
.TP
.B
+--show-below-main=3D<yes|no> [default: no]
+When enabled, this option causes full stack backtraces to be emited,
+including the part before \fBmain\fP in your program (subject to the
+\fB--num-callers\fP option.) When disabled, only the part of the stack
+backtrace up to and including main is printed.
+
+.TP
+.B
--suppressions=3D<filename> [default: $PREFIX/lib/\fBvalgrind\fP/default=
.supp]
Specifies an extra file from which to read descriptions of errors to
suppress. You may specify up to 10 additional suppression files.
=20
.TP
.B
+--time-stamp=3D<yes|no> [default: no]
+When enabled, a time-stamp is added to all log messages.
+
+.TP
+.B
--tool=3D<toolname> [default: memcheck]
Specify which tool to use. The default tool is memcheck.
=20
@@ -328,14 +388,6 @@
errors to be reported by \fBmemcheck\fP, so it's usually a good idea to
leave this enabled.
=20
-.TP
-.B
---cleanup=3D<yes|no> [default: yes]
-\fBThis is a flag to help debug valgrind itself. It is of no use to
-end-users\fP. When enabled, various improvments are applied to the
-post-instrumented intermediate code, aimed at removing redundant value
-checks.
-
.SH CACHEGRIND OPTIONS
=20
.TP
@@ -425,7 +477,7 @@
.B
--alignment=3D<number> [default: 8]
By default \fBvalgrind\fP's malloc, realloc, etc, return 8-byte aligned
-addresses. These are suitable for any accesses on x86 processors. Some
+addresses. These are suitable for any accesses on most processors. Some
programs might however assume that malloc et al return 16- or more
aligned memory. These programs are broken and should be fixed, but if
this is impossible for whatever reason the alignment can be increased
@@ -434,100 +486,6 @@
=20
.TP
.B
---branchpred=3D<yes|no> [default: no]
-This option enables the generation of static branch prediction hints.
-In theory this allows the real CPU to do a better job of running the
-generated code, but in practice it makes almost no measurable difference=
.
-It may have a large effect on some x86 implementations.
-
-.TP
-.B
---chain-bb=3D<yes|no> [default: yes]
-Enables basic-block chaining. If basic-block chaining is disabled,
-the synthetic CPU returns to the scheduler after interpreting each basic
-block. With basic block chaining enabled, it can immediately proceed to
-the next basic block. This almost always results in a performance gain,
-so it is enabled by default.
-
-.TP
-.B
---command-line-only=3D<yes|no> [default: no]
-Normally, \fBvalgrind\fP will look for command-line options in the
-following locations:
-.RS
-.TP
-- The \fBvalgrind\fP command line
-.TP
-- The \fB\.valgrindrc\fP file in the invocation directory
-.TP
-- The \fB\.valgrindrc\fP file in users home directory
-.TP
-- The \fB$VALGRIND_OPTS\fP environment variable
-.P
-
-When this option is enabled, \fBvalgrind\fP will only look at the comman=
d
-line for options.
-.RE
-
-.TP
-.B
---demangle=3D<yes|no> [default: yes]
-Enable or disable automatic demangling (decoding) of C++ names. Enabled =
by
-default. When enabled, \fBvalgrind\fP will attempt to translate encoded
-C++ procedure names back to something approaching the original. The
-demangler handles symbols mangled by g++ versions 2.X and 3.X.
-
-.TP
-.B
---dump-error=3D<number>
-After the program has exited, show gory details of the translation of
-the basic block containing the \fB<number>\fP'th error context. When
-used with --single-step=3Dyes, can show the exact x86 instruction causin=
g
-an error. This is all fairly dodgy and doesn't work at all if threads
-are involved.
-
-.TP
-.B
---exec=3D<filename>
-Specify the executable to run. If this is specified, it takes precedence
-over the \fByour-program\fP executable from the command-line. If this i=
s
-not specified, \fBvalgrind\fP searches the path for the \fByour-program\=
fP
-executable, just like a regular shell would.
-
-.TP
-.B
---input-fd=3D<number> [default: 0, stdin]
-Specify the file descriptor to use for reading input from the user. This
-is used whenever \fBvalgrind\fP needs to prompt the user for a decision.
-
-.TP
-.B
---log-fd=3D<number> [default: 2, stderr]
-Specifies that \fBvalgrind\fP should send all of its messages to
-the specified file descriptor. The default, 2, is the standard error
-channel (stderr). Note that this may interfere with the client's own
-use of stderr.
-
-.TP
-.B
---log-socket=3D<ip-address:port-number>
-Specifies that \fBvalgrind\fP should send all of its messages to the
-specified port at the specified IP address. The port may be omitted,
-in which case port 1500 is used. If a connection cannot be made to
-the specified socket, \fBvalgrind\fP falls back to writing output to
-the standard error (stderr). This option is intended to be used in
-conjunction with the \fBvalgrind-listener\fP program. For further detail=
s,
-see section 2.3 of the user manual.
-
-.TP
-.B
---optimise=3D<yes|no> [default: yes]
-When enabled, various improvements are applied to the intermediate code,
-mainly aimed at allowing the simulated CPU's registers to be cached in
-the real CPU's registers over several simulated instructions.
-
-.TP
-.B
--pointercheck=3D<yes|no> [default: yes]
When enabled, enforces client address space limits. If this option is
disabled, the client program has full and unfettered access to the part
@@ -563,27 +521,6 @@
=20
.TP
.B
---show-below-main=3D<yes|no> [default: no]
-When enabled, this option causes full stack backtraces to be emited,
-including the part before \fBmain\fP in your program (subject to the
-\fB--num-callers\fP option.) When disabled, only the part of the stack
-backtrace up to and including main is printed.
-
-.TP
-.B
---single-step=3D<yes|no> [default: no]
-When enabled, each x86 insn is translated separately into instrumented
-code. When disabled, translation is done on a per-basic-block basis,
-giving much better translations. This is needed when running
-\fBvalgrind\fP under \fBvalgrind\fP.
-
-.TP
-.B
---time-stamp=3D<yes|no> [default: no]
-When enabled, a time-stamp is added to all log messages.
-
-.TP
-.B
--weird-hacks=3Dhack1,hack2,\.\.\.
Pass miscellaneous hints to \fBvalgrind\fP which slightly modify the
simulated behaviour in nonstandard or dangerous ways, possibly to help
@@ -609,72 +546,8 @@
=20
.TP
.B
---profile=3D<yes|no> [default: no]
-When enabled, does crude internal profiling of \fBvalgrind\fP itself. Th=
is
-is not for profiling your programs. Rather it is to allow the developers
-to assess where \fBvalgrind\fP is spending its time. The tools must be
-built for profiling for this to work.
+Valgrind has several debugging options that are mostly of use to develop=
ers. Use \fB--help-debug\fB to show them.
=20
-.TP
-.B
---sanity-level=3D<number> [default: 1]
-Set the level of sanity checking to perform. This is used for debugging
-\fBvalgrind\fP. Setting this to 2 or higher can cause more internal
-sanity checks to be performed, but can slow your program down
-appreciably. Setting this to 0 disables sanity checks.
-
-.TP
-.B
---trace-codegen=3D<bitmask>
-Produce lots of output showing exactly how \fBvalgrind\fP is translating
-each basic block. The argument to this option is a 5-bit wide bitmask.
-Each bit refers to a specific feature to trace. If the bit is 1, the
-feature is traced. If it is 0, the feature is not traced.
-
-.RS
-The traced features are:
-.TP
-Bit 1: basic-block disassembly
-.TP
-Bit 2: optimization phase
-.TP
-Bit 3: tool instrumentation
-.TP
-Bit 4: register allocation
-.TP
-Bit 5: final code generation
-.RE
-
-.TP
-.B
---trace-malloc=3D<yes|no> [default: no]
-Enable or disable tracing of malloc, free and other memory-manager calls=
.
-
-.TP
-.B
---trace-redir=3D<yes|no> [default: no]
-Enable or disable tracing of function redirection.
-
-.TP
-.B
---trace-sched=3D<yes|no> [default: no]
-Enable or disable tracing of thread scheduling events.
-
-.TP
-.B
---trace-signals=3D<yes|no> [default: no]
-Enable or disable tracing of signal handling.
-
-.TP
-.B
---trace-syscalls=3D<yes|no> [default: no]
-Enable or disable tracing of system call intercepts.
-
-.TP
-.B
---trace-symtab=3D<yes|no> [default: no]
-Enable or disable tracing of symbol table reading.
-
.SH SEE ALSO
/usr/share/doc/\fBvalgrind\fP/html/manual.html
=20
Modified: trunk/docs/xml/manual-core.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/manual-core.xml 2005-07-25 23:18:04 UTC (rev 4258)
+++ trunk/docs/xml/manual-core.xml 2005-07-25 23:18:44 UTC (rev 4259)
@@ -610,6 +610,13 @@
</listitem>
=20
<listitem>
+ <para><computeroutput>-q --quiet</computeroutput></para>
+ <para>Run silently, and only print error messages. Useful if
+ you are running regression tests or have some other automated
+ test machinery.</para>
+ </listitem>
+
+ <listitem>
<para><computeroutput>-v --verbose</computeroutput></para>
<para>Be more verbose. Gives extra information on various
aspects of your program, such as: the shared objects loaded,
@@ -619,13 +626,6 @@
</listitem>
=20
<listitem>
- <para><computeroutput>-q --quiet</computeroutput></para>
- <para>Run silently, and only print error messages. Useful if
- you are running regression tests or have some other automated
- test machinery.</para>
- </listitem>
-
- <listitem>
<para><computeroutput>--trace-children=3Dno</computeroutput>
[default]</para>
<para><computeroutput>--trace-children=3Dyes</computeroutput></para>
@@ -635,6 +635,23 @@
</listitem>
=20
<listitem>
+ <para><computeroutput>--track-fds=3Dno</computeroutput> [default]</p=
ara>
+ <para><computeroutput>--track-fds=3Dyes</computeroutput></para>
+ <para>When enabled, Valgrind will print out a list of open
+ file descriptors on exit. Along with each file descriptor,
+ Valgrind prints out a stack backtrace of where the file was
+ opened and any details relating to the file descriptor such
+ as the file name or socket details.</para>
+ </listitem>
+
+ <listitem>
+ <para><computeroutput>--time-stamp=3Dno</computeroutput> [default]</=
para>
+ <para><computeroutput>--time-stamp=3Dyes</computeroutput></para>
+ <para>When enabled, Valgrind will precede each message with the
+ current time and date.</para>
+ </listitem>
+
+ <listitem>
<para><computeroutput>--log-fd=3D<number></computeroutput>
[default: 2, stderr]</para>
<para>Specifies that Valgrind should send all of its messages
@@ -696,6 +713,23 @@
<itemizedlist>
=20
<listitem>
+ <para><computeroutput>--xml=3Dno</computeroutput> [default]</para>
+ <para><computeroutput>--xml=3Dyes</computeroutput></para>
+ <para>When enabled, output will be in XML format. This is aimed at
+ making life easier for tools that consume Valgrind's output as input=
,
+ such as GUI front ends. Currently this option only works with Memch=
eck
+ and Nulgrind.
+ </para>
+ </listitem>
+ =20
+ <listitem>
+ <para><computeroutput>--xml-user-comment=3D<string></computero=
utput> [default=3D""]</para>
+ <para>Embeds an extra user comment string in the XML output. Only w=
orks
+ with <computeroutput>--xml=3Dyes</computeroutput> is specified; ign=
ored
+ otherwise.</para>
+ </listitem>
+ =20
+ <listitem>
<para><computeroutput>--demangle=3Dno</computeroutput></para>
<para><computeroutput>--demangle=3Dyes</computeroutput> [default]</p=
ara>
<para>Disable/enable automatic demangling (decoding) of C++
@@ -802,48 +836,6 @@
</listitem>
=20
<listitem>
- <para><computeroutput>--track-fds=3Dno</computeroutput> [default]</p=
ara>
- <para><computeroutput>--track-fds=3Dyes</computeroutput></para>
- <para>When enabled, Valgrind will print out a list of open
- file descriptors on exit. Along with each file descriptor,
- Valgrind prints out a stack backtrace of where the file was
- opened and any details relating to the file descriptor such
- as the file name or socket details.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--max-stackframe=3D<number></computerout=
put>
- [default=3D2000000]
- </para>
- <para>You may need to use this option if your program has large
- stack-allocated arrays. Valgrind keeps track of your program's
- stack pointer. If it changes by more than the threshold amount,
- Valgrind assumes your program is switching to a different stack,
- and Memcheck behaves differently than it would for a stack pointer
- change smaller than the threshold. Usually this heuristic works
- well. However, if your program allocates large structures on the
- stack, this heuristic will be fooled, and Memcheck will
- subsequently report large numbers of invalid stack accesses. This
- option allows you to change the threshold to a different value.
- </para>
- <para>
- You should only consider use of this flag if Valgrind's debug output
- directs you to do so. In that case it will tell you the new
- threshold you should specify.
- </para>
- <para>
- In general, allocating large structures on the stack is a bad
- idea, because (1) you can easily run out of stack space,
- especially on systems with limited memory or which expect to
- support large numbers of threads each with a small stack, and (2)
- because the error checking performed by Memcheck is more effective
- for heap-allocated data than for stack-allocated data. If you
- have to use this flag, you may wish to consider rewriting your
- code to allocate on the heap rather than on the stack.
- </para>
- </listitem>
-
- <listitem>
<para><computeroutput>--db-attach=3Dno</computeroutput> [default]</p=
ara>
<para><computeroutput>--db-attach=3Dyes</computeroutput></para>
<para>When enabled, Valgrind will pause after every error
@@ -910,6 +902,38 @@
alternative file descriptor from which to read input.</para>
</listitem>
=20
+ <listitem>
+ <para><computeroutput>--max-stackframe=3D<number></computerout=
put>
+ [default=3D2000000]
+ </para>
+ <para>You may need to use this option if your program has large
+ stack-allocated arrays. Valgrind keeps track of your program's
+ stack pointer. If it changes by more than the threshold amount,
+ Valgrind assumes your program is switching to a different stack,
+ and Memcheck behaves differently than it would for a stack pointer
+ change smaller than the threshold. Usually this heuristic works
+ well. However, if your program allocates large structures on the
+ stack, this heuristic will be fooled, and Memcheck will
+ subsequently report large numbers of invalid stack accesses. This
+ option allows you to change the threshold to a different value.
+ </para>
+ <para>
+ You should only consider use of this flag if Valgrind's debug output
+ directs you to do so. In that case it will tell you the new
+ threshold you should specify.
+ </para>
+ <para>
+ In general, allocating large structures on the stack is a bad
+ idea, because (1) you can easily run out of stack space,
+ especially on systems with limited memory or which expect to
+ support large numbers of threads each with a small stack, and (2)
+ because the error checking performed by Memcheck is more effective
+ for heap-allocated data than for stack-allocated data. If you
+ have to use this flag, you may wish to consider rewriting your
+ code to allocate on the heap rather than on the stack.
+ </para>
+ </listitem>
+
</itemizedlist>
</sect2>
=20
@@ -940,8 +964,8 @@
</sect2>
=20
=20
- <sect2 id=3D"manual-core.rareopts" xreflabel=3D"Rare Options">
- <title>Rare Options</title>
+ <sect2 id=3D"manual-core.rareopts" xreflabel=3D"Uncommon Options">
+ <title>Uncommon Options</title>
=20
<para>These options apply to all tools, as they affect certain
obscure workings of the Valgrind core. Most people won't need
@@ -1027,6 +1051,27 @@
the same functionality.</para>
</listitem>
=20
+ <listitem>
+ <para><computeroutput>--show-emwarns=3Dno</computeroutput> [default]=
</para>
+ <para><computeroutput>--show-emwarns=3Dyes</computeroutput></para>
+ <para>When enabled, Valgrind will emit warnings about its CPU emulat=
ion
+ in certain cases. These are usually not interesting.</para>
+ </listitem>
+
+ <listitem>
+ <para><computeroutput>--smc-check=3Dnone</computeroutput></para>
+ <para><computeroutput>--smc-check=3Dstack</computeroutput> [default]=
</para>
+ <para><computeroutput>--smc-check=3Dall</computeroutput></para>
+ <para>This option controls Valgrind's detection of self-modifying co=
de.
+ Valgrind can do no detection, detect self-modifying code on the stac=
k,
+ or detect self-modifying code anywhere. Note that the default optio=
n
+ will catch the vast majority of cases, as far as we know. Running w=
ith
+ <computeroutput>all</computeroutput> will slow Valgrind down greatly
+ (but running with <computeroutput>none</computeroutput> will rarely
+ speed things up, since very little code gets put on the stack for mo=
st
+ programs). </para>
+ </listitem>
+
</itemizedlist>
</sect2>
=20
@@ -1035,123 +1080,10 @@
<title>Debugging Valgrind Options</title>
=20
<para>There are also some options for debugging Valgrind itself.
-You shouldn't need to use them in the normal run of things.
-Nevertheless:</para>
+You shouldn't need to use them in the normal run of things. If you
+wish to see the list, use the <computeroutput>--help-debug</computeroutp=
ut>
+option.</para>
=20
- <itemizedlist>
-
- <listitem>
- <para><computeroutput>--single-step=3Dno</computeroutput>
- [default]</para>
- <para><computeroutput>--single-step=3Dyes</computeroutput></para>
- <para>When enabled, each instruction is translated separately
- into instrumented code. When disabled, translation is done
- on a per-basic-block basis, giving much better
- translations. This option is very useful if your program expects
- precise exceptions (if it, for example, inspects or modifies registe=
r
- state from within a signal handler).
- </para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--optimise=3Dno</computeroutput></para>
- <para><computeroutput>--optimise=3Dyes</computeroutput> [default]</p=
ara>
- <para>When enabled, various improvements are applied to the
- intermediate code, mainly aimed at allowing the simulated
- CPU's registers to be cached in the real CPU's registers over
- several simulated instructions.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--profile=3Dno</computeroutput></para>
- <para><computeroutput>--profile=3Dyes</computeroutput> [default]</pa=
ra>
- <para>When enabled, does crude internal profiling of Valgrind
- itself. This is not for profiling your programs. Rather it
- is to allow the developers to assess where Valgrind is
- spending its time. The tools must be built for profiling for
- this to work.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-syscalls=3Dno</computeroutput>
- [default]</para>
- <para><computeroutput>--trace-syscalls=3Dyes</computeroutput></para>
- <para>Enable/disable tracing of system call intercepts.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-signals=3Dno</computeroutput>
- [default]</para>
- <para><computeroutput>--trace-signals=3Dyes</computeroutput></para>
- <para>Enable/disable tracing of signal handling.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-sched=3Dno</computeroutput>
- [default]</para>
- <para><computeroutput>--trace-sched=3Dyes</computeroutput></para>
- <para>Enable/disable tracing of thread scheduling events.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-pthread=3Dnone</computeroutput>
- [default]</para>
- <para><computeroutput>--trace-pthread=3Dsome</computeroutput></para>
- <para><computeroutput>--trace-pthread=3Dall</computeroutput></para>
- <para>Specifies amount of trace detail for pthread-related
- events.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-symtab=3Dno</computeroutput>
- [default]</para>
- <para><computeroutput>--trace-symtab=3Dyes</computeroutput></para>
- <para>Enable/disable tracing of symbol table reading and line
- number info reading.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-cfi=3Dno</computeroutput>
- [default]</para>
- <para><computeroutput>--trace-cfi=3Dyes</computeroutput></para>
- <para>Enable/disable tracing of call-frame-info reading.
- Call-frame-info (CFI) is information inserted by compilers=20
- which describes the relationship between adjacent call frames.
- On architectures which by default do not use a frame pointer,=20
- such as AMD64, this information is essential for creating stack=20
- snapshots.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-malloc=3Dno</computeroutput>
- [default]</para>
- <para><computeroutput>--trace-malloc=3Dyes</computeroutput></para>
- <para>Enable/disable tracing of malloc/free (et al)
- intercepts.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--trace-codegen=3DXXXXX</computeroutput>
- [default: 00000]</para>
- <para>Enable/disable tracing of code generation. Code can be
- printed at five different stages of translation; each
- <computeroutput>X</computeroutput> element must be 0 or
- 1.</para>
- </listitem>
-
- <listitem>
- <para><computeroutput>--dump-error=3D<number></computeroutput>
- [default: inactive]</para>
- <para>After the program has exited, show gory details of the
- translation of the basic block containing the <number>'th
- error context. When used with
- <computeroutput>--single-step=3Dyes</computeroutput>, can show
- the exact instruction causing an error. This is all
- fairly dodgy and doesn't work at all if threads are
- involved.</para>
- </listitem>
-
- </itemizedlist>
</sect2>
=20
=20
Modified: trunk/memcheck/docs/mc-manual.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/memcheck/docs/mc-manual.xml 2005-07-25 23:18:04 UTC (rev 4258)
+++ trunk/memcheck/docs/mc-manual.xml 2005-07-25 23:18:44 UTC (rev 4259)
@@ -62,15 +62,18 @@
<itemizedlist id=3D"leakcheck">
<listitem>
<para><computeroutput>--leak-check=3Dno</computeroutput>
+ <para><computeroutput>--leak-check=3Dsummary</computeroutput>
[default]</para>
- <para><computeroutput>--leak-check=3Dyes</computeroutput></para>
+ <para><computeroutput>--leak-check=3Dfull</computeroutput></para>
<para>When enabled, search for memory leaks when the client
program finishes. A memory leak means a malloc'd block,
which has not yet been free'd, but to which no pointer can be
found. Such a block can never be free'd by the program,
- since no pointer to it exists. Leak checking is disabled by
- default because it tends to generate dozens of error
- messages.</para>
+ since no pointer to it exists. If set to
+ <computeroutput>summary</computeroutput>, it says how many leaks occ=
urred.
+ If set to <computeroutput>all</computeroutput>, it gives details of =
each
+ individual leak.</para>
+
</listitem>
=20
<listitem id=3D"showreach">
@@ -182,15 +185,6 @@
enabled.</para>
</listitem>
=20
- <listitem id=3D"cleanup">
- <para><computeroutput>--cleanup=3Dno</computeroutput></para>
- <para><computeroutput>--cleanup=3Dyes</computeroutput> [default]</pa=
ra>
- <para><command>This is a flag to help debug valgrind itself.
- It is of no use to end-users.</command> When enabled, various
- improvments are applied to the post-instrumented intermediate
- code, aimed at removing redundant value checks.</para>
- </listitem>
-
</itemizedlist>
</sect1>
=20
|
|
From: <sv...@va...> - 2005-07-25 23:18:09
|
Author: njn
Date: 2005-07-26 00:18:04 +0100 (Tue, 26 Jul 2005)
New Revision: 4258
Log:
Tweak order of Memcheck's cmd-line options.
Modified:
trunk/memcheck/mac_shared.c
Modified: trunk/memcheck/mac_shared.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/memcheck/mac_shared.c 2005-07-25 23:01:43 UTC (rev 4257)
+++ trunk/memcheck/mac_shared.c 2005-07-25 23:18:04 UTC (rev 4258)
@@ -97,11 +97,11 @@
void MAC_(print_common_usage)(void)
{
VG_(printf)(
-" --partial-loads-ok=3Dno|yes too hard to explain here; see ma=
nual [yes]\n"
-" --freelist-vol=3D<number> volume of freed blocks queue [10=
00000]\n"
" --leak-check=3Dno|summary|full search for memory leaks at exit?=
[summary]\n"
" --leak-resolution=3Dlow|med|high how much bt merging in leak chec=
k [low]\n"
" --show-reachable=3Dno|yes show reachable blocks in leak ch=
eck? [no]\n"
+" --partial-loads-ok=3Dno|yes too hard to explain here; see ma=
nual [yes]\n"
+" --freelist-vol=3D<number> volume of freed blocks queue [10=
00000]\n"
" --workaround-gcc296-bugs=3Dno|yes self explanatory [no]\n"
);
VG_(replacement_malloc_print_usage)();
|
|
From: <sv...@va...> - 2005-07-25 23:01:48
|
Author: sewardj Date: 2005-07-26 00:01:43 +0100 (Tue, 26 Jul 2005) New Revision: 4257 Log: Build the .ps/.pdf documentation by default when doing 'make dist'. Because this means installing lots of XML processing tools and supporting gunk, there is a hack at the top of docs/Makefile.am for disabling the .pdf/.ps build. Modified: trunk/docs/Makefile.am Modified: trunk/docs/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/docs/Makefile.am 2005-07-25 22:36:52 UTC (rev 4256) +++ trunk/docs/Makefile.am 2005-07-25 23:01:43 UTC (rev 4257) @@ -1,3 +1,19 @@ + +##------------------------------------------------------------- +## HACK: stuff to avoid making the print docs if installing the +## tools to do so is impractical / too difficult +##------------------------------------------------------------- + +# Comment out the next line to skip building print docs. The default +# is not to skip building print docs. Note, after changing it +# you of course need to re-run configure to make it take effect. +BUILD_ALL_DOCS=3Dyes + +##------------------------------------------------------------- +## END OF HACK +##------------------------------------------------------------- + + SUBDIRS =3D xml lib images internals =20 EXTRA_DIST =3D README @@ -4,6 +20,7 @@ =20 dist_man_MANS =3D valgrind.1 =20 + ##------------------------------------------------------------------- ## Below here is more ordinary make stuff... ##------------------------------------------------------------------- @@ -70,14 +87,40 @@ # If the docs have been built, install them. But don't worry if they ha= ve=20 # not -- developers do 'make install' not from a 'make dist'-ified distr= o all # the time. +# +# Note: this is done at 'make install' time. +# Note 2: the ifeq/else/endif have to be indented one space=20 +# because otherwise it seems that automake thinks it should +# be the one to handle the else/endif parts, not GNU make +# as we intend. install-data-hook: if test -r html ; then \ mkdir -p $(DESTDIR)$(datadir)/doc/valgrind/; \ cp -r html $(DESTDIR)$(datadir)/doc/valgrind/; \ fi + ifeq ($(BUILD_ALL_DOCS),yes) + if test -r index.pdf ; then \ + mkdir -p $(DESTDIR)$(datadir)/doc/valgrind/; \ + cp index.pdf $(DESTDIR)$(datadir)/doc/valgrind/; \ + fi + if test -r index.ps ; then \ + mkdir -p $(DESTDIR)$(datadir)/doc/valgrind/; \ + cp index.ps $(DESTDIR)$(datadir)/doc/valgrind/; \ + fi + endif =20 + +# This is done at 'make dist' time. It builds the html and print docs +# and copies them into the docs/ directory in the tarball. + ifeq ($(BUILD_ALL_DOCS),yes) +dist-hook: html-docs print-docs + cp -r html $(distdir) + cp print/index.pdf $(distdir) + cp print/index.ps $(distdir) + else dist-hook: html-docs - cp -r html $(distdir)=09 + cp -r html $(distdir) + endif =20 distclean-local: rm -rf html print |
|
From: <sv...@va...> - 2005-07-25 22:37:07
|
Author: njn
Date: 2005-07-25 23:36:52 +0100 (Mon, 25 Jul 2005)
New Revision: 4256
Log:
Recategorise options in the usage message.
Modified:
trunk/coregrind/m_main.c
trunk/none/tests/cmdline1.stdout.exp
trunk/none/tests/cmdline2.stdout.exp
Modified: trunk/coregrind/m_main.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/m_main.c 2005-07-25 21:12:40 UTC (rev 4255)
+++ trunk/coregrind/m_main.c 2005-07-25 22:36:52 UTC (rev 4256)
@@ -1263,6 +1263,11 @@
" --trace-children=3Dno|yes Valgrind-ise child processes? [no]\n"
" --track-fds=3Dno|yes track open file descriptors? [no]\n"
" --time-stamp=3Dno|yes add timestamps to log messages? [no]\n"
+" --log-fd=3D<number> log messages to file descriptor [2=3Dst=
derr]\n"
+" --log-file=3D<file> log messages to <file>.pid<pid>\n"
+" --log-file-exactly=3D<file> log messages to <file>\n"
+" --log-file-qualifier=3D<VAR> incorporate $VAR in logfile name [none=
]\n"
+" --log-socket=3Dipaddr:port log messages to socket ipaddr:port\n"
"\n"
" uncommon user options for all Valgrind tools:\n"
" --run-libc-freeres=3Dno|yes free up glibc memory at exit? [yes]\n"
@@ -1273,13 +1278,8 @@
" only for code found in stacks, or all [st=
ack]\n"
"\n"
" user options for Valgrind tools that report errors:\n"
-" --xml=3Dyes all output is in XML (Memcheck only)\n"
+" --xml=3Dyes all output is in XML (Memcheck/Nulgrind=
only)\n"
" --xml-user-comment=3DSTR copy STR verbatim to XML output\n"
-" --log-fd=3D<number> log messages to file descriptor [2=3Dst=
derr]\n"
-" --log-file=3D<file> log messages to <file>.pid<pid>\n"
-" --log-file-exactly=3D<file> log messages to <file>\n"
-" --log-file-qualifier=3D<VAR> incorporate $VAR in logfile name [none=
]\n"
-" --log-socket=3Dipaddr:port log messages to socket ipaddr:port\n"
" --demangle=3Dno|yes automatically demangle C++ names? [yes]=
\n"
" --num-callers=3D<number> show <num> callers in stack traces [12]=
\n"
" --error-limit=3Dno|yes stop showing new errors if too many? [y=
es]\n"
Modified: trunk/none/tests/cmdline1.stdout.exp
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/cmdline1.stdout.exp 2005-07-25 21:12:40 UTC (rev 425=
5)
+++ trunk/none/tests/cmdline1.stdout.exp 2005-07-25 22:36:52 UTC (rev 425=
6)
@@ -10,6 +10,11 @@
--trace-children=3Dno|yes Valgrind-ise child processes? [no]
--track-fds=3Dno|yes track open file descriptors? [no]
--time-stamp=3Dno|yes add timestamps to log messages? [no]
+ --log-fd=3D<number> log messages to file descriptor [2=3Dstd=
err]
+ --log-file=3D<file> log messages to <file>.pid<pid>
+ --log-file-exactly=3D<file> log messages to <file>
+ --log-file-qualifier=3D<VAR> incorporate $VAR in logfile name [none]
+ --log-socket=3Dipaddr:port log messages to socket ipaddr:port
=20
uncommon user options for all Valgrind tools:
--run-libc-freeres=3Dno|yes free up glibc memory at exit? [yes]
@@ -20,13 +25,8 @@
only for code found in stacks, or all [sta=
ck]
=20
user options for Valgrind tools that report errors:
- --xml=3Dyes all output is in XML (Memcheck only)
+ --xml=3Dyes all output is in XML (Memcheck/Nulgrind =
only)
--xml-user-comment=3DSTR copy STR verbatim to XML output
- --log-fd=3D<number> log messages to file descriptor [2=3Dstd=
err]
- --log-file=3D<file> log messages to <file>.pid<pid>
- --log-file-exactly=3D<file> log messages to <file>
- --log-file-qualifier=3D<VAR> incorporate $VAR in logfile name [none]
- --log-socket=3Dipaddr:port log messages to socket ipaddr:port
--demangle=3Dno|yes automatically demangle C++ names? [yes]
--num-callers=3D<number> show <num> callers in stack traces [12]
--error-limit=3Dno|yes stop showing new errors if too many? [ye=
s]
Modified: trunk/none/tests/cmdline2.stdout.exp
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/none/tests/cmdline2.stdout.exp 2005-07-25 21:12:40 UTC (rev 425=
5)
+++ trunk/none/tests/cmdline2.stdout.exp 2005-07-25 22:36:52 UTC (rev 425=
6)
@@ -10,6 +10,11 @@
--trace-children=3Dno|yes Valgrind-ise child processes? [no]
--track-fds=3Dno|yes track open file descriptors? [no]
--time-stamp=3Dno|yes add timestamps to log messages? [no]
+ --log-fd=3D<number> log messages to file descriptor [2=3Dstd=
err]
+ --log-file=3D<file> log messages to <file>.pid<pid>
+ --log-file-exactly=3D<file> log messages to <file>
+ --log-file-qualifier=3D<VAR> incorporate $VAR in logfile name [none]
+ --log-socket=3Dipaddr:port log messages to socket ipaddr:port
=20
uncommon user options for all Valgrind tools:
--run-libc-freeres=3Dno|yes free up glibc memory at exit? [yes]
@@ -20,13 +25,8 @@
only for code found in stacks, or all [sta=
ck]
=20
user options for Valgrind tools that report errors:
- --xml=3Dyes all output is in XML (Memcheck only)
+ --xml=3Dyes all output is in XML (Memcheck/Nulgrind =
only)
--xml-user-comment=3DSTR copy STR verbatim to XML output
- --log-fd=3D<number> log messages to file descriptor [2=3Dstd=
err]
- --log-file=3D<file> log messages to <file>.pid<pid>
- --log-file-exactly=3D<file> log messages to <file>
- --log-file-qualifier=3D<VAR> incorporate $VAR in logfile name [none]
- --log-socket=3Dipaddr:port log messages to socket ipaddr:port
--demangle=3Dno|yes automatically demangle C++ names? [yes]
--num-callers=3D<number> show <num> callers in stack traces [12]
--error-limit=3Dno|yes stop showing new errors if too many? [ye=
s]
|
|
From: Naveen K. <g_n...@ya...> - 2005-07-25 21:28:41
|
Is there a way then that vex can inform valgrind the type of the syscall ? Instead of just saying that it is a syscall maybe give additional information specifying the actual syscall instruction like 1 for int $0xZZ 2 for sysentry 3 for lcall or something like that. Then all the additional work would have to be done in the do_syscall_for_client_WRK routine. Naveen > > > the sysenter instruction is the culprit > > > > How did you get to a sysenter instruction though? We don't support > > that and instead force all system calls to go the int $80 route. > > This is on solaris-x86. >So presumably you just need to make vex-x86 treat that >as a syscall >instruction and end the BB so valgrind gets control >and then Naveen >can worry about writing a system call handler to haul >values out of >the appropriate registers. >In principle we could use that on linux as well and >remove the hack >that forces int $80 for system calls. >Tom __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: <sv...@va...> - 2005-07-25 21:12:43
|
Author: njn Date: 2005-07-25 22:12:40 +0100 (Mon, 25 Jul 2005) New Revision: 4255 Log: Make it more obvious if something fails when making HTML or PS/PDF docs. Also put the output of all pfdxmltex runs in the logfile, not just the last run's output. Modified: trunk/docs/Makefile.am Modified: trunk/docs/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/docs/Makefile.am 2005-07-25 17:58:48 UTC (rev 4254) +++ trunk/docs/Makefile.am 2005-07-25 21:12:40 UTC (rev 4255) @@ -42,30 +42,30 @@ # chunked html html-docs: @echo "Generating html files..." - export XML_CATALOG_FILES=3D$(XML_CATALOG_FILES) - mkdir -p $(htmldir) - /bin/rm -fr $(htmldir)/ - mkdir -p $(htmldir)/ - mkdir -p $(htmldir)/images - cp $(libdir)/vg_basic.css $(htmldir)/ - cp $(imgdir)/*.png $(htmldir)/images + export XML_CATALOG_FILES=3D$(XML_CATALOG_FILES) && \ + mkdir -p $(htmldir) && \ + /bin/rm -fr $(htmldir)/ && \ + mkdir -p $(htmldir)/ && \ + mkdir -p $(htmldir)/images && \ + cp $(libdir)/vg_basic.css $(htmldir)/ && \ + cp $(imgdir)/*.png $(htmldir)/images && \ $(XSLTPROC) $(XSLTPROC_FLAGS) -o $(htmldir)/ $(XSL_HTML_CHUNK_STYLE) $(= xmldir)/index.xml =20 # pdf and postscript print-docs: @echo "Generating PDF file: $(printdir)/index.pdf (please be patient)..= ."; - export XML_CATALOG_FILES=3D$(XML_CATALOG_FILES); - mkdir -p $(printdir); - mkdir -p $(printdir)/images; - cp $(imgdir)/massif-graph-sm.png $(printdir)/images; - $(XSLTPROC) $(XSLTPROC_FLAGS) -o $(printdir)/index.fo $(XSL_FO_STYLE) $= (xmldir)/index.xml; + export XML_CATALOG_FILES=3D$(XML_CATALOG_FILES) && \ + mkdir -p $(printdir) && \ + mkdir -p $(printdir)/images && \ + cp $(imgdir)/massif-graph-sm.png $(printdir)/images && \ + $(XSLTPROC) $(XSLTPROC_FLAGS) -o $(printdir)/index.fo $(XSL_FO_STYLE) $= (xmldir)/index.xml && \ (cd $(printdir) && \ - pdfxmltex index.fo &> $(LOGFILE) && \ - pdfxmltex index.fo &> $(LOGFILE) && \ - pdfxmltex index.fo &> $(LOGFILE) && \ + ( pdfxmltex index.fo && \ + pdfxmltex index.fo && \ + pdfxmltex index.fo ) &> $(LOGFILE) && \ echo "Generating PS file: $(printdir)/index.ps ..." && \ pdftops index.pdf && \ - rm *.log *.aux *.fo *.out) + rm -f *.log *.aux *.fo *.out) =20 # If the docs have been built, install them. But don't worry if they ha= ve=20 # not -- developers do 'make install' not from a 'make dist'-ified distr= o all |
|
From: <sv...@va...> - 2005-07-25 17:59:14
|
Author: sewardj Date: 2005-07-25 18:58:48 +0100 (Mon, 25 Jul 2005) New Revision: 4254 Log: I'm still a moron (just in case anybody wondered whether things had improved since last time I was a moron. No, they haven't). Move text that's supposed to be at the top of the file to the top of the file. I need to learn about these scroll-bar things some time. Modified: trunk/docs/README Modified: trunk/docs/README =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/README 2005-07-25 17:54:06 UTC (rev 4253) +++ trunk/docs/README 2005-07-25 17:58:48 UTC (rev 4254) @@ -1,22 +1,4 @@ -Valgrind Documentation ----------------------- -This text assumes the following directory structure: =20 -Distribution text files (eg. README): - valgrind/ - -Main /docs/ dir: - valgrind/docs/ - -Top-level XML files:=20 - valgrind/docs/xml/ - -Tool specific XML docs: - valgrind/<toolname>/docs/ - -All images used in the docs: - valgrind/docs/images/ - New notes, JRS 20050727 ~~~~~~~~~~~~~~~~~~~~~~~ * I had to install zillions of packages on SuSE 9.2 in order to @@ -40,6 +22,25 @@ =20 Old notes ~~~~~~~~~ +Valgrind Documentation +---------------------- +This text assumes the following directory structure: + +Distribution text files (eg. README): + valgrind/ + +Main /docs/ dir: + valgrind/docs/ + +Top-level XML files:=20 + valgrind/docs/xml/ + +Tool specific XML docs: + valgrind/<toolname>/docs/ + +All images used in the docs: + valgrind/docs/images/ + Stylesheets, catalogs, parsing/formatting scripts: valgrind/docs/lib/ =20 |
|
From: <sv...@va...> - 2005-07-25 17:54:09
|
Author: sewardj Date: 2005-07-25 18:54:06 +0100 (Mon, 25 Jul 2005) New Revision: 4253 Log: Record my adventures in 'make print-docs' land. Modified: trunk/docs/README Modified: trunk/docs/README =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/README 2005-07-25 17:53:46 UTC (rev 4252) +++ trunk/docs/README 2005-07-25 17:54:06 UTC (rev 4253) @@ -17,6 +17,29 @@ All images used in the docs: valgrind/docs/images/ =20 +New notes, JRS 20050727 +~~~~~~~~~~~~~~~~~~~~~~~ +* I had to install zillions of packages on SuSE 9.2 in order to + build the print docs (make print-docs), including + + passivetex + xpdf (for pdftops) + + It's possible to use pdf2ps instead, but that seems to generate + huge and almost-unreadable .ps. pdftops does a much nicer job. + + +* Even then, pdfxmltex eventually dies with "TeX capacity exceeded, + sorry [pool size =3D 67555]" or some such. To fix this, I edited + /etc/texmf/texmf.cnf and changed + + pool_size.pdfxmltex =3D 500000 + + to 1500000 and that fixed it. + + +Old notes +~~~~~~~~~ Stylesheets, catalogs, parsing/formatting scripts: valgrind/docs/lib/ =20 @@ -56,9 +79,9 @@ automake target, but does nothing.) Likewise for PDF/PS with 'make print-docs'. =20 -- 'make dist' puts the XML files into the tarball. It also builds the - HTML docs and puts them in too, in valgrind/docs/html/ (including - style sheets, images, etc). +- 'make dist' (nb: at the top level, not in docs/) puts the XML files + into the tarball. It also builds the HTML docs and puts them in too,=20 + in valgrind/docs/html/ (including style sheets, images, etc). =20 - 'make install' installs the HTML docs in $(install)/share/doc/valgrind/html/, if they are present. (They will |
|
From: <sv...@va...> - 2005-07-25 17:53:55
|
Author: sewardj Date: 2005-07-25 18:53:46 +0100 (Mon, 25 Jul 2005) New Revision: 4252 Log: I think && might be a better statement-joiner than ; -- the pdfxmltex runs can easily die silently. Modified: trunk/docs/Makefile.am Modified: trunk/docs/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/docs/Makefile.am 2005-07-25 15:28:36 UTC (rev 4251) +++ trunk/docs/Makefile.am 2005-07-25 17:53:46 UTC (rev 4252) @@ -59,12 +59,12 @@ mkdir -p $(printdir)/images; cp $(imgdir)/massif-graph-sm.png $(printdir)/images; $(XSLTPROC) $(XSLTPROC_FLAGS) -o $(printdir)/index.fo $(XSL_FO_STYLE) $= (xmldir)/index.xml; - (cd $(printdir); \ - pdfxmltex index.fo &> $(LOGFILE); \ - pdfxmltex index.fo &> $(LOGFILE); \ - pdfxmltex index.fo &> $(LOGFILE); \ - echo "Generating PS file: $(printdir)/index.ps ..."; \ - pdftops index.pdf; \ + (cd $(printdir) && \ + pdfxmltex index.fo &> $(LOGFILE) && \ + pdfxmltex index.fo &> $(LOGFILE) && \ + pdfxmltex index.fo &> $(LOGFILE) && \ + echo "Generating PS file: $(printdir)/index.ps ..." && \ + pdftops index.pdf && \ rm *.log *.aux *.fo *.out) =20 # If the docs have been built, install them. But don't worry if they ha= ve=20 |
|
From: John M. <tt...@te...> - 2005-07-25 15:28:46
|
On Mon, 2005-07-25 at 16:22 +0100, Tom Hughes wrote: > In message <1122304763.4591.6.camel@localhost> > John McCutchan <tt...@te...> wrote: > > > On Mon, 2005-07-25 at 16:10 +0100, Tom Hughes wrote: > > > >> I've updated our lists of system call numbers, and I'm just fixing up > >> a couple of things in your patch before committing it but I notice > >> that you've marked inotify_init as a blocking call but it doesn't look > >> like it should block. Can you clarify when it will block? > > > > :), I really didn't know what I was doing, but sys_open, and sys_futex > > (both which can create fd's like inotify_init) say they might block. So, > > I was trying to be conservative and added that. > > Both open and futex can block - open if you are opening a pipe or > device or a network mounted file or something like that and futex > because that is it's job in life ;-) > > I've committed inotify support based on your patch now anyway. Wicked. Thanks! John McCutchan |
|
From: <sv...@va...> - 2005-07-25 15:28:38
|
Author: tom
Date: 2005-07-25 16:28:36 +0100 (Mon, 25 Jul 2005)
New Revision: 4251
Log:
Fix some inconsistent system call trace messages.
Modified:
trunk/coregrind/m_syswrap/syswrap-linux.c
Modified: trunk/coregrind/m_syswrap/syswrap-linux.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/m_syswrap/syswrap-linux.c 2005-07-25 15:21:41 UTC (re=
v 4250)
+++ trunk/coregrind/m_syswrap/syswrap-linux.c 2005-07-25 15:28:36 UTC (re=
v 4251)
@@ -787,7 +787,7 @@
{
Int i;
=20
- PRINT("sys_io_submit( %llu, %lld, %p )", (ULong)ARG1,(Long)ARG2,ARG3)=
;
+ PRINT("sys_io_submit ( %llu, %lld, %p )", (ULong)ARG1,(Long)ARG2,ARG3=
);
PRE_REG_READ3(long, "io_submit",
vki_aio_context_t, ctx_id, long, nr,
struct iocb **, iocbpp);
@@ -816,7 +816,7 @@
=20
PRE(sys_io_cancel)
{
- PRINT("sys_io_cancel( %llu, %p, %p )", (ULong)ARG1,ARG2,ARG3);
+ PRINT("sys_io_cancel ( %llu, %p, %p )", (ULong)ARG1,ARG2,ARG3);
PRE_REG_READ3(long, "io_cancel",
vki_aio_context_t, ctx_id, struct iocb *, iocb,
struct io_event *, result);
@@ -831,7 +831,7 @@
=20
PRE(sys_set_mempolicy)
{
- PRINT("sys_set_mempolicy( %d, %p, %d )", ARG1,ARG2,ARG3);
+ PRINT("sys_set_mempolicy ( %d, %p, %d )", ARG1,ARG2,ARG3);
PRE_REG_READ3(long, "set_mempolicy",
int, policy, unsigned long *, nodemask,
unsigned long, maxnode);
@@ -841,7 +841,7 @@
=20
PRE(sys_get_mempolicy)
{
- PRINT("sys_get_mempolicy( %p, %p, %d, %p, %x )", ARG1,ARG2,ARG3,ARG4,=
ARG5);
+ PRINT("sys_get_mempolicy ( %p, %p, %d, %p, %x )", ARG1,ARG2,ARG3,ARG4=
,ARG5);
PRE_REG_READ5(long, "get_mempolicy",
int *, policy, unsigned long *, nodemask,
unsigned long, maxnode, unsigned long, addr,
@@ -879,14 +879,14 @@
=20
PRE(sys_inotify_add_watch)
{
- PRINT( "sys_inotify_add_watch( %d, %p, %x )", ARG1,ARG2,ARG3);
+ PRINT( "sys_inotify_add_watch ( %d, %p, %x )", ARG1,ARG2,ARG3);
PRE_REG_READ3(long, "inotify_add_watch", int, fd, char *, path, int, =
mask);
PRE_MEM_RASCIIZ( "inotify_add_watch(path)", ARG2 );
}
=20
PRE(sys_inotify_rm_watch)
{
- PRINT( "sys_inotify_rm_watch( %d, %x )", ARG1,ARG2);
+ PRINT( "sys_inotify_rm_watch ( %d, %x )", ARG1,ARG2);
PRE_REG_READ2(long, "inotify_rm_watch", int, fd, int, wd);
}
=20
|
|
From: John M. <tt...@te...> - 2005-07-25 15:28:17
|
On Mon, 2005-07-25 at 16:22 +0100, Tom Hughes wrote: > In message <1122304763.4591.6.camel@localhost> > John McCutchan <tt...@te...> wrote: > > > On Mon, 2005-07-25 at 16:10 +0100, Tom Hughes wrote: > > > >> I've updated our lists of system call numbers, and I'm just fixing up > >> a couple of things in your patch before committing it but I notice > >> that you've marked inotify_init as a blocking call but it doesn't look > >> like it should block. Can you clarify when it will block? > > > > :), I really didn't know what I was doing, but sys_open, and sys_futex > > (both which can create fd's like inotify_init) say they might block. So, > > I was trying to be conservative and added that. > > Both open and futex can block - open if you are opening a pipe or > device or a network mounted file or something like that and futex > because that is it's job in life ;-) > > I've committed inotify support based on your patch now anyway. > > Tom > |
|
From: Tom H. <to...@co...> - 2005-07-25 15:23:06
|
In message <1122304763.4591.6.camel@localhost>
John McCutchan <tt...@te...> wrote:
> On Mon, 2005-07-25 at 16:10 +0100, Tom Hughes wrote:
>
>> I've updated our lists of system call numbers, and I'm just fixing up
>> a couple of things in your patch before committing it but I notice
>> that you've marked inotify_init as a blocking call but it doesn't look
>> like it should block. Can you clarify when it will block?
>
> :), I really didn't know what I was doing, but sys_open, and sys_futex
> (both which can create fd's like inotify_init) say they might block. So,
> I was trying to be conservative and added that.
Both open and futex can block - open if you are opening a pipe or
device or a network mounted file or something like that and futex
because that is it's job in life ;-)
I've committed inotify support based on your patch now anyway.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: <sv...@va...> - 2005-07-25 15:21:49
|
Author: tom
Date: 2005-07-25 16:21:41 +0100 (Mon, 25 Jul 2005)
New Revision: 4250
Log:
Add support for the inotify system calls based on a patch
from John McCutchan <tt...@te...>.
Modified:
trunk/coregrind/m_syswrap/priv_syswrap-linux.h
trunk/coregrind/m_syswrap/syswrap-linux.c
trunk/coregrind/m_syswrap/syswrap-x86-linux.c
Modified: trunk/coregrind/m_syswrap/priv_syswrap-linux.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/m_syswrap/priv_syswrap-linux.h 2005-07-25 15:04:00 UT=
C (rev 4249)
+++ trunk/coregrind/m_syswrap/priv_syswrap-linux.h 2005-07-25 15:21:41 UT=
C (rev 4250)
@@ -92,6 +92,10 @@
DECL_TEMPLATE(linux, sys_set_mempolicy);
DECL_TEMPLATE(linux, sys_get_mempolicy);
=20
+DECL_TEMPLATE(linux, sys_inotify_init);
+DECL_TEMPLATE(linux, sys_inotify_add_watch);
+DECL_TEMPLATE(linux, sys_inotify_rm_watch);
+
#endif // __PRIV_SYSWRAP_LINUX_H
=20
/*--------------------------------------------------------------------*/
Modified: trunk/coregrind/m_syswrap/syswrap-linux.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/m_syswrap/syswrap-linux.c 2005-07-25 15:04:00 UTC (re=
v 4249)
+++ trunk/coregrind/m_syswrap/syswrap-linux.c 2005-07-25 15:21:41 UTC (re=
v 4250)
@@ -860,6 +860,36 @@
POST_MEM_WRITE( ARG2, VG_ROUNDUP( ARG3, sizeof(UWord) * 8 ) / size=
of(UWord) );
}
=20
+PRE(sys_inotify_init)
+{
+ PRINT("sys_inotify_init ( )");
+ PRE_REG_READ0(long, "inotify_init");
+}
+POST(sys_inotify_init)
+{
+ vg_assert(SUCCESS);
+ if (!ML_(fd_allowed)(RES, "inotify_init", tid, True)) {
+ VG_(close)(RES);
+ SET_STATUS_Failure( VKI_EMFILE );
+ } else {
+ if (VG_(clo_track_fds))
+ ML_(record_fd_open_nameless) (tid, RES);
+ }
+}
+
+PRE(sys_inotify_add_watch)
+{
+ PRINT( "sys_inotify_add_watch( %d, %p, %x )", ARG1,ARG2,ARG3);
+ PRE_REG_READ3(long, "inotify_add_watch", int, fd, char *, path, int, =
mask);
+ PRE_MEM_RASCIIZ( "inotify_add_watch(path)", ARG2 );
+}
+
+PRE(sys_inotify_rm_watch)
+{
+ PRINT( "sys_inotify_rm_watch( %d, %x )", ARG1,ARG2);
+ PRE_REG_READ2(long, "inotify_rm_watch", int, fd, int, wd);
+}
+
#undef PRE
#undef POST
=20
Modified: trunk/coregrind/m_syswrap/syswrap-x86-linux.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/m_syswrap/syswrap-x86-linux.c 2005-07-25 15:04:00 UTC=
(rev 4249)
+++ trunk/coregrind/m_syswrap/syswrap-x86-linux.c 2005-07-25 15:21:41 UTC=
(rev 4250)
@@ -2277,6 +2277,18 @@
GENX_(__NR_mq_notify, sys_mq_notify), // (mq_open+4)
GENXY(__NR_mq_getsetattr, sys_mq_getsetattr), // (mq_open+5)
GENX_(__NR_sys_kexec_load, sys_ni_syscall), // 283
+// GENXY(__NR_waitid, sys_waitid), // 284
+
+ GENX_(285, sys_ni_syscall), // 285
+// LINX_(__NR_add_key, sys_add_key), // 286
+// LINX_(__NR_request_key, sys_request_key), // 287
+// LINXY(__NR_keyctl, sys_keyctl), // 288
+// LINX_(__NR_ioprio_set, sys_ioprio_set), // 289
+
+// LINX_(__NR_ioprio_get, sys_ioprio_get), // 290
+ LINX_(__NR_inotify_init, sys_inotify_init), // 291
+ LINX_(__NR_inotify_add_watch, sys_inotify_add_watch), // 292
+ LINX_(__NR_inotify_rm_watch, sys_inotify_rm_watch), // 293
};
=20
const UInt ML_(syscall_table_size) =3D=20
|
|
From: Dirk M. <dm...@gm...> - 2005-07-25 15:13:07
|
On Monday 25 July 2005 16:45, Tom Hughes wrote: > I can't see any sign of these calls in the 2.6.12 kernel source. Are > they part of the standard kernel? Its brand-new and will appear in 2.6.13 (its in vanilla tree starting with 2.6.13rc3 I think). > If not where do we find the source for them? Are the system call > numbers well defined or might the official kernel reuse them for > something else? They're the official ones. Dirk |
|
From: John M. <tt...@te...> - 2005-07-25 15:13:02
|
On Mon, 2005-07-25 at 16:10 +0100, Tom Hughes wrote: > In message <yek...@de...> > Tom Hughes <to...@co...> wrote: > > > In message <1122302613.2226.5.camel@localhost> > > John McCutchan <tt...@te...> wrote: > > > >> I've attached a patch that wraps the inotify system calls on x86 linux. > >> Please consider this for the next version of valgrind. > > > > I can't see any sign of these calls in the 2.6.12 kernel source. Are > > they part of the standard kernel? > > I've found it in the 2.6.13-rc3 source now. I notice that it's only > hooked in to the x86 system call table though. > It will be hooked into amd64 soon to. Nothing about the code is platform specific, but we are letting the platforms hook it up as they need. > I've updated our lists of system call numbers, and I'm just fixing up > a couple of things in your patch before committing it but I notice > that you've marked inotify_init as a blocking call but it doesn't look > like it should block. Can you clarify when it will block? :), I really didn't know what I was doing, but sys_open, and sys_futex (both which can create fd's like inotify_init) say they might block. So, I was trying to be conservative and added that. John McCutchan |
|
From: Tom H. <to...@co...> - 2005-07-25 15:10:12
|
In message <yek...@de...>
Tom Hughes <to...@co...> wrote:
> In message <1122302613.2226.5.camel@localhost>
> John McCutchan <tt...@te...> wrote:
>
>> I've attached a patch that wraps the inotify system calls on x86 linux.
>> Please consider this for the next version of valgrind.
>
> I can't see any sign of these calls in the 2.6.12 kernel source. Are
> they part of the standard kernel?
I've found it in the 2.6.13-rc3 source now. I notice that it's only
hooked in to the x86 system call table though.
I've updated our lists of system call numbers, and I'm just fixing up
a couple of things in your patch before committing it but I notice
that you've marked inotify_init as a blocking call but it doesn't look
like it should block. Can you clarify when it will block?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: John M. <tt...@te...> - 2005-07-25 15:08:50
|
On Mon, 2005-07-25 at 15:45 +0100, Tom Hughes wrote: > In message <1122302613.2226.5.camel@localhost> > John McCutchan <tt...@te...> wrote: > > > I've attached a patch that wraps the inotify system calls on x86 linux. > > Please consider this for the next version of valgrind. > > I can't see any sign of these calls in the 2.6.12 kernel source. Are > they part of the standard kernel? > Inotify will be part of 2.6.13 > If not where do we find the source for them? Are the system call > numbers well defined or might the official kernel reuse them for > something else? I notice that you haven't defined any constants > for the call numbers and have just put in manifest constants? The system call numbers are defined in 2.6.13. They are not going to be reused for anything. John |
|
From: Christian P. <tr...@ge...> - 2005-07-25 15:07:39
|
On Monday 25 July 2005 16:45, Tom Hughes wrote: > In message <1122302613.2226.5.camel@localhost> > > John McCutchan <tt...@te...> wrote: > > I've attached a patch that wraps the inotify system calls on x86 linux. > > Please consider this for the next version of valgrind. > > I can't see any sign of these calls in the 2.6.12 kernel source. Are > they part of the standard kernel? > > If not where do we find the source for them? Are the system call > numbers well defined or might the official kernel reuse them for > something else? I notice that you haven't defined any constants > for the call numbers and have just put in manifest constants? > > Tom Hmm.... looks like a patch, but a very promising one: http://www.kernel.org/pub/linux/kernel/people/rml/inotify/v2.6/0.24/inotify= =2D0.24-rml-2.6.13-rc2-4.patch Articles about: http://kerneltrap.org/node/3847 http://www-128.ibm.com/developerworks/linux/library/l-inotify.html?ca=3Ddgr= =2Dlnxw52Inotify http://lwn.net/Articles/104343/ Although, I thought about playing around with it a bit, too(!). The gentoo-sources Linux kernel includes this patch already. Googling aroun= d=20 has shown me that debian *seems* to have it too. Regards, Christian Parpart. =2D-=20 16:54:56 up 124 days, 6:02, 2 users, load average: 3.61, 3.43, 3.83 |
|
From: <sv...@va...> - 2005-07-25 15:04:06
|
Author: tom Date: 2005-07-25 16:04:00 +0100 (Mon, 25 Jul 2005) New Revision: 4249 Log: Update unistd headers to match the 2.6.13-rc3 kernel source. Modified: trunk/coregrind/vki_unistd-amd64-linux.h trunk/coregrind/vki_unistd-ppc32-linux.h trunk/coregrind/vki_unistd-x86-linux.h Modified: trunk/coregrind/vki_unistd-amd64-linux.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/vki_unistd-amd64-linux.h 2005-07-25 12:49:39 UTC (rev= 4248) +++ trunk/coregrind/vki_unistd-amd64-linux.h 2005-07-25 15:04:00 UTC (rev= 4249) @@ -324,6 +324,10 @@ #define __NR_mq_getsetattr 245 #define __NR_kexec_load 246 #define __NR_waitid 247 +#define __NR_add_key 248 +#define __NR_request_key 249 +#define __NR_keyctl 250 +#define __NR_ioprio_set 251 +#define __NR_ioprio_get 252 =20 - #endif /* __VKI_UNISTD_AMD64_LINUX_H */ Modified: trunk/coregrind/vki_unistd-ppc32-linux.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/vki_unistd-ppc32-linux.h 2005-07-25 12:49:39 UTC (rev= 4248) +++ trunk/coregrind/vki_unistd-ppc32-linux.h 2005-07-25 15:04:00 UTC (rev= 4249) @@ -298,5 +298,11 @@ //#define __NR_mq_notify 266 //#define __NR_mq_getsetattr 267 //#define __NR_kexec_load 268 +//#define __NR_add_key 269 +//#define __NR_request_key 270 +//#define __NR_keyctl 271 +//#define __NR_waitid 272 +//#define __NR_ioprio_set 273 +//#define __NR_ioprio_get 274 =20 #endif /* __VKI_UNISTD_PPC32_LINUX_H */ Modified: trunk/coregrind/vki_unistd-x86-linux.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/coregrind/vki_unistd-x86-linux.h 2005-07-25 12:49:39 UTC (rev 4= 248) +++ trunk/coregrind/vki_unistd-x86-linux.h 2005-07-25 15:04:00 UTC (rev 4= 249) @@ -280,7 +280,7 @@ #define __NR_io_submit 248 #define __NR_io_cancel 249 #define __NR_fadvise64 250 - +#define __NR_set_zone_reclaim 251 #define __NR_exit_group 252 #define __NR_lookup_dcookie 253 #define __NR_epoll_create 254 @@ -313,6 +313,15 @@ #define __NR_mq_notify (__NR_mq_open+4) #define __NR_mq_getsetattr (__NR_mq_open+5) #define __NR_sys_kexec_load 283 -#define __NR_wait 284 +#define __NR_waitid 284 +/* #define __NR_sys_setaltroot 285 */ +#define __NR_add_key 286 +#define __NR_request_key 287 +#define __NR_keyctl 288 +#define __NR_ioprio_set 289 +#define __NR_ioprio_get 290 +#define __NR_inotify_init 291 +#define __NR_inotify_add_watch 292 +#define __NR_inotify_rm_watch 293 =20 #endif /* __VKI_UNISTD_X86_LINUX_H */ |
|
From: Tom H. <to...@co...> - 2005-07-25 14:45:19
|
In message <1122302613.2226.5.camel@localhost>
John McCutchan <tt...@te...> wrote:
> I've attached a patch that wraps the inotify system calls on x86 linux.
> Please consider this for the next version of valgrind.
I can't see any sign of these calls in the 2.6.12 kernel source. Are
they part of the standard kernel?
If not where do we find the source for them? Are the system call
numbers well defined or might the official kernel reuse them for
something else? I notice that you haven't defined any constants
for the call numbers and have just put in manifest constants?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|