|
From: Dirk M. <mu...@kd...> - 2003-11-06 23:13:10
|
CVS commit by mueller: valgrind homepage A index.html 1.1 |
|
From: Nicholas N. <nj...@ca...> - 2003-11-09 15:06:56
|
CVS commit by nethercote: Tiny test change to Valgrind site. M +2 -2 index.html 1.2 --- devel-home/valgrind/index.html #1.1:1.2 @@ -40,6 +40,6 @@ and our time resources are limited, with the result that we're providing a poorer and poorer service replying to mail messages. One -aim of this list is, therefore, to try and foster a more -self-supporting Valgrind user community. +aim of this list is to try and foster a more self-supporting Valgrind user +community. |
|
From: Nicholas N. <nj...@ca...> - 2003-11-10 17:55:48
|
CVS commit by nethercote: Committing completely revamped version of website. It uses frames to provide the menu, but I think Dirk is going to change it soon to use PHP. A bugs.html 1.1 A cvs.html 1.1 A docs.html 1.1 A downloads.html 1.1 A features.html 1.1 A feedback.html 1.1 A home.html 1.1 A lists.html 1.1 A menu.html 1.1 A overview.html 1.1 A related.html 1.1 A sysreqs.html 1.1 A tools.html 1.1 M +18 -281 index.html 1.3 |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 00:25:33
|
CVS commit by mueller: add common header/footer A footer.inc 1.1 A header.inc 1.1 A menu.inc 1.1 M +6 -7 bugs.html 1.2 --- devel-home/valgrind/bugs.html #1.1:1.2 @@ -1,9 +1,6 @@ -<html> -<head> -<title>Valgrind: Bug Reports</title> -<link rel="stylesheet" type="text/css" href="style.css"> -</head> +<?php + include "header.inc" +?> -<body> <center><h1>Valgrind</h1></center> @@ -27,3 +24,5 @@ <hr> -</body> +<?php + include "footer.inc" +?> |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 00:43:36
|
CVS commit by mueller: convert webpage M +6 -9 cvs.html 1.2 M +7 -9 docs.html 1.2 M +6 -8 downloads.html 1.2 M +8 -8 features.html 1.2 M +7 -8 feedback.html 1.2 M +1 -0 footer.inc 1.2 M +6 -2 header.inc 1.2 M +8 -8 home.html 1.2 M +6 -10 lists.html 1.2 M +1 -1 menu.inc 1.2 M +8 -9 overview.html 1.2 M +6 -9 related.html 1.2 M +6 -8 sysreqs.html 1.2 M +7 -8 tools.html 1.2 R menu.html 1.1 |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 00:44:33
|
CVS commit by mueller: d'oh M +0 -1 header.inc 1.3 --- devel-home/valgrind/header.inc #1.2:1.3 @@ -9,5 +9,4 @@ <tr><td bgcolor="#eeeeee"> -<div align="left"> <?php include "menu.inc" |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 00:45:49
|
CVS commit by mueller: d'oh^3 M +1 -1 header.inc 1.5 --- devel-home/valgrind/header.inc #1.4:1.5 @@ -7,5 +7,5 @@ <body> <table width="100%" cellspacing=10> -<tr><td bgcolor="#eeeeee"> +<tr><td bgcolor="#eeeeee" valign="top"> <?php |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 00:45:20
|
CVS commit by mueller: d'oh^2 M +1 -1 header.inc 1.4 --- devel-home/valgrind/header.inc #1.3:1.4 @@ -13,3 +13,3 @@ ?> -</td> +</td><td> |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 00:46:38
|
CVS commit by mueller: fix link M +1 -1 downloads.html 1.3 --- devel-home/valgrind/downloads.html #1.2:1.3 @@ -42,5 +42,5 @@ <b>20031012-wine (of mid Oct 2003)</b> - <a HREF="valgrind-20031012-wine.tar.bz2">(bzip2'd source, 697KB)</a> + <a HREF="http://developer.kde.org/~sewardj/valgrind-20031012-wine.tar.bz2">(bzip2'd source, 697KB)</a> (MD5=ebe1641b4873ec30dd013b6b618f5f90) <p> |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 00:49:14
|
CVS commit by mueller: remove frames M +33 -17 index.html 1.4 M +1 -1 menu.inc 1.3 R home.html 1.2 --- devel-home/valgrind/index.html #1.3:1.4 @@ -1,18 +1,34 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN" "http://www.w3.org/TR/html4/frameset.dtd"> -<html> -<head> -<title>Valgrind: an open-source debugging and profiling system for x86-Linux</title> -<link rel="stylesheet" type="text/css" href="style.css"> -<base target="_top"> -</head> +<?php + include "header.inc" +?> + +<center><h1>Valgrind</h1></center> + +<hr> +<center><h2>News</h2></center> +<center>November 9, 2003: A new stable release, 2.0.0, is available.</center> +<p> + +<hr> +<p> +<b>Valgrind is a system for debugging and profiling x86-Linux programs.</b> +With the tools that come with Valgrind, you can automatically detect +many memory management and threading bugs, avoiding hours of frustrating +bug-hunting, making your programs more stable. You can also perform +detailed profiling to help speed up your programs. +<p> +The Valgrind distribution include four tools: two memory error +detectors, a thread error detector, and a cache profiler. Several other +tools have been built with Valgrind. +<p> +Use the menu at left to learn more. +<p> +<hr> +<font size="-1"> +Feedback about website to Nick Nethercote (njn25 at cam dot ac dot uk). +</font> + +<?php + include "footer.inc" +?> -<frameset cols="*,3*"> - <frame name="contents" src="menu.html" scrolling="auto"> - <frame name="main" src="home.html" scrolling="auto"> - <noframes> - <body> - <p>This page uses frames, but your browser doesn't support them.</p> - </body> - </noframes> -</frameset> -</html> --- devel-home/valgrind/menu.inc #1.2:1.3 @@ -1,3 +1,3 @@ - <a href="home.html"> Home </a> + <a href="/"> Home </a> <br><a href="overview.html"> Overview </a> <br><a href="tools.html"> Tools </a> |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 01:01:06
|
CVS commit by mueller: add FAQ A faq.html 1.1 M +1 -1 bugs.html 1.3 M +1 -1 menu.inc 1.4 --- devel-home/valgrind/bugs.html #1.2:1.3 @@ -9,5 +9,5 @@ Before you report a bug, please consult the -<a HREF="docs-20031012/FAQ.txt">Frequently Asked Questions</a>. It +<a HREF="faq.html">Frequently Asked Questions</a>. It contains workarounds for more or less all the failure conditions for which we know a workaround. This includes a large fraction of the --- devel-home/valgrind/menu.inc #1.3:1.4 @@ -5,5 +5,5 @@ <br><a href="docs.html"> Documentation </a> <br><a href="downloads.html">Downloads </a> -<br><a href="docs-20031012/FAQ.txt">FAQ </a> +<br><a href="faq.html">FAQ </a> <br><a href="bugs.html"> Bug Reports </a> <br><a href="features.html"> Feature Requests</a> |
|
From: Julian S. <js...@ac...> - 2003-11-11 01:11:29
|
CVS commit by jseward: Announce 2.0.0. M +14 -16 downloads.html 1.5 M +1 -1 index.html 1.5 --- devel-home/valgrind/downloads.html #1.4:1.5 @@ -10,21 +10,19 @@ <h3>Current Stable Release</h3> -<b>20031012 (of 12 October 2003)</b> - <a HREF="http://developer.kde.org/~sewardj/valgrind-20031012.tar.bz2">(bzip2'd source, 691KB)</a> - (MD5=4a3d02cb9972af801651cf3effb005eb) +<b>2.0.0 (of 11 November 2003)</b> + <a HREF="http://developer.kde.org/~sewardj/valgrind-2.0.0.tar.bz2">(bzip2'd source, 710KB)</a> + (MD5=1f6a90d0ca494fb75eaeef498e8252b5) <p> -20031012 contains three months worth of critical bug fixes, roughly. -Most significant single change is improved SSE/SSE2 support, mostly -thanks to Dirk Mueller of KDE fame. POSIX spinlocks are also now -supported. +Compared to the previous stable release (20031012), +2.0.0 improves SSE/SSE2 support, fixes some minor bugs, and +improves support for SuSE 9 and the Red Hat "Severn" beta. + <p> -20031012 builds on Red Hat Fedora ("Severn") but doesn't really work -(curiously, Mozilla runs OK, but a modest "ls -l" bombs). I hope to -get a working version out soon. It may or may not work ok on the -forthcoming SuSE 9 -- I hear positive noises about it but haven't been -able to verify this myself, since 9 is not yet released. +2.0.0 is known to build and work well on: Red Hats 7.3, 8, 9, SuSE 8.2 +and SuSE 9.0. + <p> -See the <a HREF="docs-20031012/NEWS.txt">NEWS</a> file in the distro +See the <a HREF="http://developer.kde.org/~sewardj/docs-2.0.0/NEWS.txt">NEWS</a> file in the distro for more details. --- devel-home/valgrind/index.html #1.4:1.5 @@ -7,5 +7,5 @@ <hr> <center><h2>News</h2></center> -<center>November 9, 2003: A new stable release, 2.0.0, is available.</center> +<center>November 11, 2003: A new stable release, 2.0.0, is available.</center> <p> |
|
From: Dirk M. <mu...@kd...> - 2003-11-11 01:39:58
|
CVS commit by mueller: link downloads M +1 -1 index.html 1.6 --- devel-home/valgrind/index.html #1.5:1.6 @@ -7,5 +7,5 @@ <hr> <center><h2>News</h2></center> -<center>November 11, 2003: A new stable release, 2.0.0, is available.</center> +<center>November 11, 2003: A new stable release,<a href="/downloads.html">valgrind 2.0.0</a>, is available.</center> <p> |
|
From: Nicholas N. <nj...@ca...> - 2003-11-11 09:42:29
|
CVS commit by nethercote:
Minor HTML fix.
M +3 -2 sysreqs.html 1.3
--- devel-home/valgrind/sysreqs.html #1.2:1.3
@@ -24,8 +24,9 @@
MMX support, and pretty good SSE/SSE2 support, but some instructions
are still not handled. 3DNow! (rapidly becoming 3DThen!) is not
- supported at all.</li>
-<p>
+ supported at all.
+ <p>
<li>Support for non-POSIX signal stuff is flaky. If you stick to POSIX
signals you should be ok.
+ <p>
</ul>
<a HREF="docs-20031012/coregrind_core.html#limits">
|
|
From: Nicholas N. <nj...@ca...> - 2003-11-11 11:53:00
|
CVS commit by nethercote: Added missing CSS file A style.css 1.1 |
|
From: Nicholas N. <nj...@ca...> - 2003-11-11 12:15:05
|
CVS commit by nethercote: Added html type. Also now using the CSS. M +3 -1 header.inc 1.6 --- devel-home/valgrind/header.inc #1.5:1.6 @@ -1,6 +1,8 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" +"http://www.w3.org/TR/html4/loose.dtd"> <html> <head> <title>Valgrind: Bug Reports</title> -<!-- <link rel="stylesheet" type="text/css" href="style.css"> --> +<link rel="stylesheet" type="text/css" href="style.css"> </head> |
|
From: Nicholas N. <nj...@ca...> - 2003-11-11 23:36:41
|
CVS commit by nethercote: Menu fixes: prevent two-word options from being broken across lines. Also prevent accidental blank lines from occurring in the menu, which happened due to whitespace between the end of the option and the trailing "</a>". M +2 -1 index.html 1.7 M +14 -13 menu.inc 1.5 --- devel-home/valgrind/index.html #1.6:1.7 @@ -7,5 +7,6 @@ <hr> <center><h2>News</h2></center> -<center>November 11, 2003: A new stable release,<a href="/downloads.html">valgrind 2.0.0</a>, is available.</center> +<center>November 11, 2003: A new stable release, +<a href="/downloads.html">valgrind 2.0.0</a>, is available.</center> <p> --- devel-home/valgrind/menu.inc #1.4:1.5 @@ -1,13 +1,14 @@ - <a href="/"> Home </a> -<br><a href="overview.html"> Overview </a> -<br><a href="tools.html"> Tools </a> -<br><a href="sysreqs.html"> System Requirements</a> -<br><a href="docs.html"> Documentation </a> -<br><a href="downloads.html">Downloads </a> -<br><a href="faq.html">FAQ </a> -<br><a href="bugs.html"> Bug Reports </a> -<br><a href="features.html"> Feature Requests</a> -<br><a href="lists.html"> Mailing Lists </a> -<br><a href="cvs.html"> CVS Repository </a> -<br><a href="related.html"> Related Tools </a> -<br><a href="feedback.html"> Feedback </a> +<!-- Minor hack: " " ensures two-word options stay on a single line --> + <a href="/"> Home</a> +<br><a href="overview.html"> Overview</a> +<br><a href="tools.html"> Tools</a> +<br><a href="sysreqs.html"> System Requirements</a> +<br><a href="docs.html"> Documentation</a> +<br><a href="downloads.html">Downloads</a> +<br><a href="faq.html"> FAQ</a> +<br><a href="bugs.html"> Bug Reports</a> +<br><a href="features.html"> Feature Requests</a> +<br><a href="lists.html"> Mailing Lists</a> +<br><a href="cvs.html"> CVS Repository</a> +<br><a href="related.html"> Related Tools</a> +<br><a href="feedback.html"> Feedback</a> |
|
From: Nicholas N. <nj...@ca...> - 2003-11-12 08:52:53
|
CVS commit by nethercote: Change title of all webpages from "Valgrind: Bug Reports" to just "Valgrind". M +1 -1 header.inc 1.7 --- devel-home/valgrind/header.inc #1.6:1.7 @@ -3,5 +3,5 @@ <html> <head> -<title>Valgrind: Bug Reports</title> +<title>Valgrind</title> <link rel="stylesheet" type="text/css" href="style.css"> </head> |
|
From: Nicholas N. <nj...@ca...> - 2003-11-13 09:59:29
|
CVS commit by nethercote: consistency M +0 -1 bugs.html 1.4 --- devel-home/valgrind/bugs.html #1.3:1.4 @@ -22,5 +22,4 @@ <p> We hope to have Bugzilla set up soon to deal with bug reports. -<hr> <?php |
|
From: Nicholas N. <nj...@ca...> - 2003-11-13 10:19:33
|
CVS commit by nethercote: Moved bit about website feedback from the main page to the feedback page. Added a <hr> to the bottom of every page, because it looks nice. M +5 -1 feedback.html 1.3 M +1 -0 footer.inc 1.3 M +0 -4 index.html 1.8 --- devel-home/valgrind/feedback.html #1.2:1.3 @@ -8,5 +8,5 @@ <center><h2>Feedback</h2></center> -<h3>Random Feedback</h3> +<h3>General</h3> Praise, abuse, ideas, etc, can be sent to: <br>Julian Seward (jseward at acm dot org) @@ -14,4 +14,8 @@ <br>Jeremy Fitzhardinge (jeremy at goop dot org) <p> + +<h3>Website</h3> +Please send feedback about this website to Nick Nethercote +(njn25 at cam dot ac dot uk). <h3>Survey</h3> --- devel-home/valgrind/footer.inc #1.2:1.3 @@ -1,2 +1,3 @@ +<hr> </tr></table> </body> --- devel-home/valgrind/index.html #1.7:1.8 @@ -25,8 +25,4 @@ Use the menu at left to learn more. <p> -<hr> -<font size="-1"> -Feedback about website to Nick Nethercote (njn25 at cam dot ac dot uk). -</font> <?php |
|
From: Nicholas N. <nj...@ca...> - 2003-11-13 10:32:42
|
CVS commit by nethercote: Fix menu so there's no blank line after "System Requirements" when viewed with Konqueror. M +15 -13 menu.inc 1.6 --- devel-home/valgrind/menu.inc #1.5:1.6 @@ -1,14 +1,16 @@ <!-- Minor hack: " " ensures two-word options stay on a single line --> - <a href="/"> Home</a> -<br><a href="overview.html"> Overview</a> -<br><a href="tools.html"> Tools</a> -<br><a href="sysreqs.html"> System Requirements</a> -<br><a href="docs.html"> Documentation</a> -<br><a href="downloads.html">Downloads</a> -<br><a href="faq.html"> FAQ</a> -<br><a href="bugs.html"> Bug Reports</a> -<br><a href="features.html"> Feature Requests</a> -<br><a href="lists.html"> Mailing Lists</a> -<br><a href="cvs.html"> CVS Repository</a> -<br><a href="related.html"> Related Tools</a> -<br><a href="feedback.html"> Feedback</a> +<dl> +<dt><a href="/"> Home</a> +<dt><a href="overview.html"> Overview</a> +<dt><a href="tools.html"> Tools</a> +<dt><a href="sysreqs.html"> System Requirements</a> +<dt><a href="docs.html"> Documentation</a> +<dt><a href="downloads.html">Downloads</a> +<dt><a href="faq.html"> FAQ</a> +<dt><a href="bugs.html"> Bug Reports</a> +<dt><a href="features.html"> Feature Requests</a> +<dt><a href="lists.html"> Mailing Lists</a> +<dt><a href="cvs.html"> CVS Repository</a> +<dt><a href="related.html"> Related Tools</a> +<dt><a href="feedback.html"> Feedback</a> +</dl> |
|
From: Nicholas N. <nj...@ca...> - 2003-11-13 12:39:42
|
CVS commit by nethercote: Changed the broken links to refer to 2.0.0 instead of 20031012. Assuming I've go them right, Julian now just needs to drop the right files into the right places on developer.kde.org/~sewardj. M +5 -3 docs.html 1.3 M +1 -1 sysreqs.html 1.4 --- devel-home/valgrind/docs.html #1.2:1.3 @@ -8,9 +8,11 @@ <center><h2>Documentation</h2></center> -<a HREF="docs-20031012/manual.html">Full documentation</a> for version -20031012 is supplied, up to date as of 12 October 2003. +<a href="http://developer.kde.org/~sewardj/docs-2.0.0/manual.html">Full +documentation</a> for version 2.0.0 is supplied, up to date as of 11 November +2003. <p> The overly-curious may want to read -<a HREF="docs-20031012/mc_techdocs.html">detailed tech docs</a> about how +<a href="http://developer.kde.org/~sewardj/docs-2.0.0/mc_techdocs.html"> +detailed tech docs</a> about how Valgrind is implemented. --- devel-home/valgrind/sysreqs.html #1.3:1.4 @@ -30,5 +30,5 @@ <p> </ul> -<a HREF="docs-20031012/coregrind_core.html#limits"> +<a href="http://developer.kde.org/~sewardj/docs-2.0.0/coregrind_core.html#limits"> Section 2.12 of the manual</a> contains a complete list of limitations. <p> |
|
From: Dirk M. <dm...@gm...> - 2003-11-13 19:11:02
|
On Thursday 13 November 2003 13:39, Nicholas Nethercote wrote: > Changed the broken links to refer to 2.0.0 instead of 20031012. Assuming > I've go them right, Julian now just needs to drop the right files into the > right places on developer.kde.org/~sewardj. imho the 2.0.0 docs should be added to the website directly, so that they can remain for historic purposes :) |
|
From: Nicholas N. <nj...@ca...> - 2003-11-15 13:04:42
|
CVS commit by nethercote: Added a comment about giving decent info when reporting bugs. M +10 -0 bugs.html 1.5 --- devel-home/valgrind/bugs.html #1.4:1.5 @@ -19,4 +19,14 @@ well be that the bug has been reported before. <p> +When you report a bug, <i>please</i> give the following information: +<ul> +<li>What version of Valgrind you are running; +<li>What command-line you are using to run Valgrind; +<li>The output of <code>valgrind -v</code>. +</ul> +It may also be useful to include your Linux version, kernel version, and glibc +version. If you include all this information, you are much more likely to get +a useful response. +<p> Patches for bugs are particularly welcome. <p> |
|
From: Nicholas N. <nj...@ca...> - 2003-11-17 11:57:34
|
CVS commit by nethercote: Added links to the new Bugzilla page from bugs.html and features.html. M +13 -10 bugs.html 1.6 M +11 -7 features.html 1.3 --- devel-home/valgrind/bugs.html #1.5:1.6 @@ -14,8 +14,14 @@ failures people seem to encounter in practice. <p> -If that fails, send it to the valgrind-users -<a href="lists.html">mailing list</a>. We try to respond to most bug -reports, but if we don't, it doesn't mean we are ignoring you; it may -well be that the bug has been reported before. +If that fails, please file a report using our +<a href="http://bugs.kde.org/enter_valgrind_bug.cgi">Bugzilla page</a>. +Patches for bugs are particularly welcome. Please note that this +Bugzilla page is new, and there may be some teething troubles. +<p> +If you have trouble with Bugzilla, or for some reason you don't think +Bugzilla is appropriate for your report (although it probably is), +contact the valgrind-users <a href="lists.html">mailing list</a>. We +try to respond to most bug reports, but if we don't, it doesn't mean we +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: @@ -25,11 +31,8 @@ <li>The output of <code>valgrind -v</code>. </ul> -It may also be useful to include your Linux version, kernel version, and glibc -version. If you include all this information, you are much more likely to get -a useful response. -<p> -Patches for bugs are particularly welcome. +It may also be useful to include your Linux version, kernel version, and +glibc version. If you include all this information, you are much more +likely to get a useful response. <p> -We hope to have Bugzilla set up soon to deal with bug reports. <?php --- devel-home/valgrind/features.html #1.2:1.3 @@ -9,8 +9,15 @@ <center><h2>Feature Requests</h2></center> -To request a feature, please email the valgrind-users <a -href="lists.html">mailing list</a>. We try to respond to most feature -requests, but if we don't, it doesn't mean we are ignoring you, rather -that we don't have any particular comments. +If that fails, please use our +<a href="http://bugs.kde.org/enter_valgrind_bug.cgi">Bugzilla page</a>; +make an entry with the severity "wishlist". Please note that this +Bugzilla page is new, and there may be some teething troubles. +<p> +If you have trouble with Bugzilla, or for some reason you don't think +Bugzilla is appropriate for your request (although it probably is), +contact the valgrind-users <a href="lists.html">mailing list</a>. We +try to respond to most feature requests, but if we don't, it doesn't +mean we are ignoring you, rather that we don't have any particular +comments. <p> Please note that we cannot satisfy many feature requests. A feature @@ -19,7 +26,4 @@ implementing a feature, that will help your chances too. <p> -We hope to have Bugzilla set up soon to deal with feature requests. -<p> - <?php |