|
From: Nicholas N. <nj...@ca...> - 2004-02-11 14:15:43
|
CVS commit by nethercote: Fix some not-so-nice HTML: - convert <i> to <em> - convert <b> to <strong> - start using style sheet properly, to remove deprecated tags like <center> M +1 -1 bugs.html 1.9 M +1 -1 cvs.html 1.5 M +3 -3 downloads.html 1.9 M +3 -3 header.inc 1.10 M +7 -14 index.html 1.16 M +20 -20 overview.html 1.11 M +1 -1 related.html 1.10 M +15 -1 style.css 1.2 M +4 -4 tools.html 1.5 --- devel-home/valgrind/bugs.html #1.8:1.9 @@ -21,5 +21,5 @@ are ignoring you; it may well be that the bug has been reported before. <p> -When you report a bug, <i>please</i> give the following information: +When you report a bug, <em>please</em> give the following information: <ul> <li>What version of Valgrind you are running; --- devel-home/valgrind/cvs.html #1.4:1.5 @@ -7,5 +7,5 @@ If you want a bleeding-edge version of Valgrind, follow these <a href="http://developer.kde.org/source/anoncvs.html">instructions</a> -to check out the HEAD from our CVS repository; the <i>modulename</i> is +to check out the HEAD from our CVS repository; the <em>modulename</em> is <code>valgrind</code>. Note particularly the information about mirrors. <p> --- devel-home/valgrind/downloads.html #1.8:1.9 @@ -7,5 +7,5 @@ <h3>Current Stable Release</h3> -<b>2.0.0 (of 11 November 2003)</b> +<strong>2.0.0 (of 11 November 2003)</strong> <a HREF="http://developer.kde.org/~sewardj/valgrind-2.0.0.tar.bz2">(bzip2'd source, 710KB)</a> (MD5=1f6a90d0ca494fb75eaeef498e8252b5) @@ -30,5 +30,5 @@ <h3>Development Releases</h3> -<b>2.1.0 (of 14 December 2003)</b> +<strong>2.1.0 (of 14 December 2003)</strong> <a HREF="http://developer.kde.org/~sewardj/valgrind-2.1.0.tar.bz2">(bzip2'd source, 762KB)</a> (MD5=3e4056dd45163a5f555a23ced2f95191) @@ -50,5 +50,5 @@ <p> -<b>20031012-wine (of mid Oct 2003)</b> +<strong>20031012-wine (of mid Oct 2003)</strong> <a HREF="http://developer.kde.org/~sewardj/valgrind-20031012-wine.tar.bz2">(bzip2'd source, 697KB)</a> --- devel-home/valgrind/header.inc #1.9:1.10 @@ -9,5 +9,5 @@ <table width="100%" cellspacing=10> <tr> -<td bgcolor="#eeeeee" valign="top"> +<td class="menu" valign="top"> <?php include "menu.inc" @@ -16,6 +16,6 @@ <td> -<center><h1>Valgrind</h1></center> +<h1>Valgrind</h1> <hr> -<center><h2><?php print $page_heading; ?></h2></center> +<h2><?php print $page_heading; ?></h2> --- devel-home/valgrind/index.html #1.15:1.16 @@ -5,28 +5,22 @@ ?> -<center>January 27, 2004: We have a new page listing +<p class="news">January 27, 2004: We have a new page listing <a href="users.html">projects using Valgrind</a>. Please see the bottom of that page if you want to add your project to the list. -</center> -<p> -<center>January 15, 2004: Valgrind awarded a merit (bronze) +<p class="news">January 15, 2004: Valgrind awarded a merit (bronze) <a href="http://opensource.org/OSA/awards.php">Open Source Award</a>. Read the <a href="http://builder.com.com/5100-6375-5136747.html">interview</a> with Julian Seward. -</center> -<p> -<center>December 14, 2003: A new unstable release, -<a href="/downloads.html">valgrind 2.1.0</a>, is available.</center> -<p> +<p class="news">December 14, 2003: A new unstable release, +<a href="/downloads.html">valgrind 2.1.0</a>, is available. -<center>November 11, 2003: A new stable release, -<a href="/downloads.html">valgrind 2.0.0</a>, is available.</center> -<p> +<p class="news">November 11, 2003: A new stable release, +<a href="/downloads.html">valgrind 2.0.0</a>, is available. <hr> <p> -<b>Valgrind is a GPL'd system for debugging and profiling x86-Linux programs.</b> +<strong>Valgrind is a GPL'd system for debugging and profiling x86-Linux programs.</strong> With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating @@ -39,5 +33,4 @@ <p> Use the menu at left to learn more. -<p> <?php --- devel-home/valgrind/overview.html #1.10:1.11 @@ -5,5 +5,5 @@ ?> -<b>Valgrind is a GPL'd system for debugging and profiling x86-Linux programs.</b> +<strong>Valgrind is a GPL'd system for debugging and profiling x86-Linux programs.</strong> With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating @@ -15,5 +15,5 @@ <ul> -<li><b>Valgrind will save you hours of debugging time.</b> +<li><strong>Valgrind will save you hours of debugging time.</strong> With Valgrind tools you can automatically detect many memory management and threading bugs. This gives you confidence that your @@ -23,15 +23,15 @@ <p> -<li><b>Valgrind can help you speed up your programs.</b> +<li><strong>Valgrind can help you speed up your programs.</strong> With Valgrind tools you can also perform very detailed profiling to help speed up your programs. <p> -<li><b>Valgrind is free.</b> Free-as-in-speech: you can download it, read +<li><strong>Valgrind is free.</strong> Free-as-in-speech: you can download it, read the source code, make modifications, and pass them on, all within the limits of the GNU GPL. And free-as-in-beer: we aren't charging for it. <p> -<li><b>Valgrind runs on x86-Linux.</b> One of the most popular platforms in +<li><strong>Valgrind runs on x86-Linux.</strong> One of the most popular platforms in use. Valgrind works on all x86-compatible machines, and works with all the major Linux distributions, including Red Hat, SuSE, Debian, Gentoo, @@ -39,5 +39,5 @@ <p> -<li><b>Valgrind is easy to use.</b> Valgrind uses dynamic binary +<li><strong>Valgrind is easy to use.</strong> Valgrind uses dynamic binary translation, so you don't need to modify, recompile or relink your applications. Just prefix your command line with @@ -45,5 +45,5 @@ <p> -<li><b>Valgrind is not a toy.</b> Valgrind is first and foremost a +<li><strong>Valgrind is not a toy.</strong> Valgrind is first and foremost a debugging and profiling system for large, complex programs. We have had feedback from users working on projects with up to 25 million @@ -56,5 +56,5 @@ <p> -<li><b>Valgrind is suitable for any type of software.</b> Valgrind has been +<li><strong>Valgrind is suitable for any type of software.</strong> Valgrind has been used on almost every kind of software imaginable: desktop applications, libraries, databases, games, web browsers, network @@ -68,5 +68,5 @@ <p> -<li><b>Valgrind is widely used.</b> Valgrind has been used by thousands +<li><strong>Valgrind is widely used.</strong> Valgrind has been used by thousands of programmers across the world. We have received feedback from users in over 25 countries, including: Belgium, Czech Republic, @@ -77,5 +77,5 @@ <p> -<li><b>Valgrind works with programs written in any language.</b> +<li><strong>Valgrind works with programs written in any language.</strong> Because Valgrind works directly with program binaries, it works with programs written in any programming language, be they compiled, @@ -89,5 +89,5 @@ <p> -<li><b>Valgrind debugs and profiles your <i>entire</i> program.</b> +<li><strong>Valgrind debugs and profiles your <em>entire</em> program.</strong> Unlike tools that require a recompilation step, Valgrind gives you total debugging and profiling coverage of every instruction executed by @@ -96,5 +96,5 @@ <p> -<li><b>Valgrind can be used with other tools.</b> Valgrind can start GDB and +<li><strong>Valgrind can be used with other tools.</strong> Valgrind can start GDB and attach it to your program at the point(s) where errors are detected, so that you can poke around and figure out what was going on at the @@ -102,5 +102,5 @@ <p> -<li><b>Valgrind is extensible.</b> Valgrind consists of the Valgrind core, +<li><strong>Valgrind is extensible.</strong> Valgrind consists of the Valgrind core, which provides a synthetic software x86 CPU, and Valgrind tools, which plug into the core, and instrument and analyse the running @@ -111,5 +111,5 @@ <p> -<li><b>Valgrind is actively maintained.</b> The Valgrind developers are +<li><strong>Valgrind is actively maintained.</strong> The Valgrind developers are constantly working to fix bugs, improve Valgrind, and ensure it works as new Linux distributions and libraries come out. There are @@ -133,23 +133,23 @@ <ul> -<li><b>All the time.</b> For small programs with short run-times, when +<li><strong>All the time.</strong> For small programs with short run-times, when developing you can always run the program under a Valgrind tool (usually either Memcheck or Addrcheck), knowing that memory bugs will be found immediately. <p> -<li><b>In automatic testing.</b> By using Valgrind tools in your +<li><strong>In automatic testing.</strong> By using Valgrind tools in your automatic unit, integration, system, or regression test, you can be confident no code will be unchecked. <p> -<li><b>After big changes.</b> To ensure new bugs haven't been introduced +<li><strong>After big changes.</strong> To ensure new bugs haven't been introduced in the new code. <p> -<li><b>When a bug occurs.</b> Get instant feedback about what the bug +<li><strong>When a bug occurs.</strong> Get instant feedback about what the bug is, where it occurred, and why. <p> -<li><b>When a bug is suspected.</b> Is your program behaving oddly? +<li><strong>When a bug is suspected.</strong> Is your program behaving oddly? Use a Valgrind tool to discover if a bug is the cause. <p> -<li><b>Before a release.</b> To give you confidence that your new +<li><strong>Before a release.</strong> To give you confidence that your new release is as stable and bug-free as possible. <p> --- devel-home/valgrind/related.html #1.9:1.10 @@ -72,5 +72,5 @@ We haven't tried the following ports, but they don't seem complete. But kudos -to the authors for attempting a <i>very</i> difficult task. +to the authors for attempting a <em>very</em> difficult task. <ul> --- devel-home/valgrind/style.css #1.1:1.2 @@ -1,2 +1,16 @@ -body { background: #ffffff; } +body { + background: #ffffff; + color: #000000; +} + +td.menu { + background: #eeeeee; + color: #000000; +} + +h1,h2 { text-align: center; } + +p.news { text-align: center; } + + --- devel-home/valgrind/tools.html #1.4:1.5 @@ -8,5 +8,5 @@ <ul> -<li><b>Memcheck</b> detects memory-management problems, and is aimed +<li><strong>Memcheck</strong> detects memory-management problems, and is aimed primarily at C and C++ programs. When a program is run under Memcheck's supervision, all reads and writes of memory are checked, @@ -36,5 +36,5 @@ programs about 10--30x slower than normal. -<li><b>Addrcheck</b> is a lightweight version of Memcheck which does +<li><strong>Addrcheck</strong> is a lightweight version of Memcheck which does no uninitialised-value checking. So it detects fewer errors than Memcheck, but programs run about twice as fast as they do on @@ -47,5 +47,5 @@ <p> -<li><b>Cachegrind</b> is a cache profiler. It performs detailed +<li><strong>Cachegrind</strong> is a cache profiler. It performs detailed simulation of the I1, D1 and L2 caches in your CPU and so can accurately pinpoint the sources of cache misses in your code. It @@ -57,5 +57,5 @@ <p> -<li><b>Helgrind</b> is a thread debugger which finds data races in +<li><strong>Helgrind</strong> is a thread debugger which finds data races in multithreaded programs. It looks for memory locations which are accessed by more than one (POSIX p-)thread, but for which no |