+
cg_annotate program. Source files to annotate can be
@@ -66,14 +65,14 @@ The two steps are:
This step can be performed as many times as you like for each Step 2. You may want to do multiple annotations showing - different information each time.
-
-The steps are described in detail in the following sections.
+The steps are described in detail in the following sections. -
- + property.
+ +
- +
+ from L1. Ditto AMD Durons and most modern VIAs.
The cache configuration simulated (cache size, associativity and line size) is
@@ -108,8 +109,9 @@ an early incarnation that doesn't give any cache information, then Cachegrind
will fall back to using a default configuration (that of a model 3/4 Athlon).
Cachegrind will tell you if this happens. You can manually specify one, two or
all three levels (I1/D1/L2) of the cache from the command line using the
---I1, --D1 and --L2 options.
+--I1, --D1 and --L2 options.
+
Other noteworthy behaviour:
+ +
inc and
dec) are counted as doing just a read, ie. a single data
reference. This may seem strange, but since the write can never cause a
miss (the read guarantees the block is in the cache) it's not very
- interesting.- + interesting. +
Thus it measures not the number of times the data cache is accessed, but the number of times a data cache miss could occur.
L2i) misses.
-
+number of L2 instruction (L2i) misses.
+
Cache accesses for data follow. The information is similar to that of the
instruction fetches, except that the values are also shown split between reads
and writes (note each row's rd and wr values add up
-to the row's total).
- -Combined instruction and data figures for the L2 cache follow that.
+to the row's total). +
+Combined instruction and data figures for the L2 cache follow that.
cachegrind.out.pid file:
is run, and will overwrite any existing
cachegrind.out.pid in the current directory (but
that won't happen very often because it takes some time for process ids
- to be recycled).
- + to be recycled).
ls -l generates a file of about
350KB. Browsing a few files and web pages with a Konqueror
built with full debugging information generates a file
diff --git a/coregrind/docs/coregrind_skins.html b/coregrind/docs/coregrind_skins.html
index 291dd3a06..a2b807e27 100644
--- a/coregrind/docs/coregrind_skins.html
+++ b/coregrind/docs/coregrind_skins.html
@@ -175,7 +175,7 @@ three spaces in which program code executes:
--skin option to the valgrind startup script. The
default skin used is memcheck, Valgrind's original memory checker.
-
+
TAG has the form VALGRIND_X_Y_Z for
version X.Y.Z.
-
+
automake and autoconf for the
@@ -532,7 +532,7 @@ These just prepend longer strings in front of names to avoid potential
namespace clashes. We strongly recommend using the SK_ macro
for any global functions and variables in your skin.- +
and rebuild Valgrind.
@@ -594,7 +595,7 @@ The other debugging command line options can be useful too (run
-
+
-
+
-
+
-jseward@acm.org
@@ -363,7 +363,7 @@ performance or functionality. As a result:
valgrind
Once a skin becomes more complicated, there are some extra things you may
want/need to do.
-
+
VG_(signalreturn_bogusRA), and checks all jumps to see
+3.1 Suppressions
If your skin reports errors and you want to suppress some common ones, you can
@@ -603,7 +604,7 @@ add suppressions to the suppression files. The relevant files are
these files by combining the relevant .supp files depending on the
versions of linux, X and glibc on a system.
-
+
3.2 Documentation
If you are feeling conscientious and want to write some HTML documentation for
@@ -636,7 +637,7 @@ name again):
3.3 Regression tests
Valgrind has some support for regression tests. If you want to write
@@ -673,7 +674,7 @@ regression tests for your skin:
3.4 Profiling
To do simple tick-based profiling of a skin, include the line
@@ -691,7 +692,7 @@ core profiling event numbers. See include/vg_skin.h for details
and the ``memcheck'' skin for an example.
-
+
3.5 Other makefile hackery
If you add any directories under valgrind/foobar/, you will
@@ -704,7 +705,7 @@ add them to the bin_SCRIPTS variable in
valgrind/foobar/Makefile.am.3.5 Core/skin interface versions
In order to allow for the core/skin interface to evolve over time, Valgrind
diff --git a/memcheck/docs/mc_techdocs.html b/memcheck/docs/mc_techdocs.html
index cd426f5ef..7b60bfc36 100644
--- a/memcheck/docs/mc_techdocs.html
+++ b/memcheck/docs/mc_techdocs.html
@@ -32,7 +32,7 @@ Detailed technical notes for hackers, maintainers and the
overly-curious
These notes pertain to snapshot 20020306
+jseward@acm.org
http://developer.kde.org/~sewardj
Copyright © 2000-2002 Julian Seward
VG_(dispatch), checks
that translations do not set %ebp to any value
different from VG_EBP_DISPATCH_CHECKED or
- & VG_(baseBlock). In effect this test is free,
+ & VG_(baseBlock). In effect this test is free,
and is permanently engaged.
UCode operand tags: type
UCode is, more or less, a simple two-address RISC-like code. In
-keeping with the x86 AT&T assembly syntax, generally speaking the
+keeping with the x86 AT&T assembly syntax, generally speaking the
first operand is the source operand, and the second is the destination
operand, which is modified when the uinstr is notionally executed.
@@ -1725,7 +1725,7 @@ Every 1000 basic blocks, we see if more signals have arrived. If so,
TagVG_(deliver_signals) builds signal delivery frames on the
client's stack, and allows their handlers to be run. Valgrind places
in these signal delivery frames a bogus return address,
-VG_(signalreturn_bogusRA), and checks all jumps to see
if any jump to it. If so, this is a sign that a signal handler is
returning, and if so Valgrind removes the relevant signal frame from
the client's stack, restores the from the signal frame the simulated
@@ -2051,9 +2051,9 @@ void fooble ( void )
int spacer1;
int b[10];
int spacer2;
- VALGRIND_MAKE_NOACCESS(&spacer0, sizeof(int));
- VALGRIND_MAKE_NOACCESS(&spacer1, sizeof(int));
- VALGRIND_MAKE_NOACCESS(&spacer2, sizeof(int));
+ VALGRIND_MAKE_NOACCESS(&spacer0, sizeof(int));
+ VALGRIND_MAKE_NOACCESS(&spacer1, sizeof(int));
+ VALGRIND_MAKE_NOACCESS(&spacer2, sizeof(int));
a[10] = 99;
}