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
(6) |
2
(3) |
3
|
4
(3) |
5
(10) |
6
(4) |
7
(5) |
|
8
(1) |
9
(3) |
10
(11) |
11
(18) |
12
(13) |
13
(4) |
14
(11) |
|
15
(12) |
16
(6) |
17
(1) |
18
(13) |
19
(14) |
20
(12) |
21
(3) |
|
22
(17) |
23
(18) |
24
(17) |
25
(24) |
26
(15) |
27
(7) |
28
(23) |
|
29
(31) |
|
|
|
|
|
|
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 23:34:26
|
CVS commit by nethercote: Heroic patch from Tom Hughes: This patch adds translation tests for most of the basic x86 instructions and fixes a few missing/broken instructions to work properly. M +1 -1 coregrind/vg_from_ucode.c 1.74 M +72 -5 coregrind/vg_helpers.S 1.31 M +9 -2 coregrind/vg_include.h 1.180 M +14 -3 coregrind/vg_main.c 1.145 M +80 -17 coregrind/vg_to_ucode.c 1.129 M +1 -1 coregrind/vg_translate.c 1.70 M +10 -2 include/vg_skin.h.base 1.12 M +6 -4 memcheck/mc_translate.c 1.36 M +18 -1 none/tests/Makefile.am 1.24 M +360 -124 none/tests/gen_insn_test.pl 1.2 M +103 -103 none/tests/insn_mmx.def 1.2 M +141 -141 none/tests/insn_sse.def 1.2 M +292 -292 none/tests/insn_sse2.def 1.2 M +24 -13 tests/cputest.c 1.2 [POSSIBLY UNSAFE: printf] |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 23:27:28
|
On Wed, 11 Feb 2004, Ayodele Thomas wrote: > Is there any way to go beyond 2GB on 32-bit linux, or is that just a > fundamental limit? I thought you could get up to 3GB by default. And I believe there are kernel patches that let you use the full 4GB; I'm sure others will know more than me. N |
|
From: Robert W. <rj...@du...> - 2004-02-11 22:46:22
|
> Significant rewrites. Apart from the new instructions, one big issue is > that Valgrind assumes 4-byte pointers in many places, unfortunately. It > might be possible to run 32-bit code on an Opteron -- but I'm not sure > about that -- but that probably won't help you. Tried and failed :-( It gets confused while parsing /proc/X/maps. I didn't have a huge amount of time to look at it, but I might get around to it in the next month or so. |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 22:38:34
|
CVS commit by nethercote: Added Anarchy Online. M +3 -0 users.html 1.39 --- devel-home/valgrind/users.html #1.38:1.39 @@ -292,4 +292,7 @@ <dd>An online multi-player tactical warfare game. +<dt><a href="http://www.anarchy-online.com">Anarchy Online</a> +<dd>An award-winning massive multiplayer online roleplaying game (MMORPG). + <dt><a href="http://crystal.sf.net">Crystal Space</a> <dd>A portable 3D game engine. |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 22:34:49
|
On Wed, 11 Feb 2004, Ayodele Thomas wrote: > I am having problems running out of the 2GB space allocated to valgrind > internally (using VG_(malloc) etc.) because my skin keeps track of a > tremendous amount of state. We are considering purchasing a an Opteron > box with Linux. The question is, would the change from 32-bit to 64-bit > Linux be a relatively easy change for Valgrind, or will it require > significant rewrites. Significant rewrites. Apart from the new instructions, one big issue is that Valgrind assumes 4-byte pointers in many places, unfortunately. It might be possible to run 32-bit code on an Opteron -- but I'm not sure about that -- but that probably won't help you. N |
|
From: Ayodele T. <em...@st...> - 2004-02-11 21:31:51
|
I am having problems running out of the 2GB space allocated to valgrind internally (using VG_(malloc) etc.) because my skin keeps track of a tremendous amount of state. We are considering purchasing a an Opteron box with Linux. The question is, would the change from 32-bit to 64-bit Linux be a relatively easy change for Valgrind, or will it require significant rewrites. Ayodele --------------------------------------------------------------- Ayodele Bolaji Thomas "Joy in the Morning" Ph.D. Candidate Electrical Engineering Computer Systems Laboratory Stanford University Ayo...@st... Support our troops. Support our country. Pray for Peace. \o/ "We succeed, not because of Affirmative Action, but in spite of the conditions that make it necessary" (ABE '98) "War may sometimes be a necessary evil. But no matter how necessary, it is always an evil, never a good. We will not learn to live together in peace by killing each other's children." Jimmy Carter '02 --------------------------------------------------------------- |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 17:54:29
|
CVS commit by nethercote: Move from HTML 4.01 transitional to HTML 4.01 strict. M +2 -1 header.inc 1.11 --- devel-home/valgrind/header.inc #1.10:1.11 @@ -1,3 +1,4 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> + <html> <head> |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 17:51:55
|
CVS commit by nethercote:
<b> --> <strong>
M +5 -5 menu.inc 1.13
--- devel-home/valgrind/menu.inc #1.12:1.13
@@ -2,5 +2,5 @@
line, and also so that there's a blank line between sections. -->
<dl>
-<dt><b>About</b>
+<dt><strong>About</strong>
<dt><a href="index.html"> Home</a>
<dt><a href="overview.html"> Overview</a>
@@ -8,10 +8,10 @@
<dt><a href="related.html"> Related Projects</a>
<dt>
-<dt><b>Code</b>
+<dt><strong>Code</strong>
<dt><a href="sysreqs.html"> System Requirements</a>
<dt><a href="downloads.html">Downloads</a>
<dt><a href="cvs.html"> CVS Repository</a>
<dt>
-<dt><b>Support</b>
+<dt><strong>Support</strong>
<dt><a href="docs.html"> Documentation</a>
<dt><a href="lists.html"> Mailing Lists</a>
@@ -20,10 +20,10 @@
<dt><a href="features.html"> Feature Requests</a>
<dt>
-<dt><b>Proselytism</b>
+<dt><strong>Proselytism</strong>
<dt><a href="users.html"> Users</a>
<dt><a href="articles.html"> Articles</a>
<dt><a href="awards.html"> Awards</a>
<dt>
-<dt><b>Feedback</b>
+<dt><strong>Feedback</strong>
<dt><a href="surveys.html"> Surveys</a>
<dt><a href="contact.html"> Contact</a>
|
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 14:51:56
|
CVS commit by nethercote: Removing now-unnecessary <center> tags M +1 -1 overview.html 1.12 M +1 -1 tools.html 1.6 --- devel-home/valgrind/overview.html #1.11:1.12 @@ -127,5 +127,5 @@ <hr> -<center><h2>When to Use</h2></center> +<h2>When to Use</h2> When should you use Valgrind tools? It depends on your exact needs. --- devel-home/valgrind/tools.html #1.5:1.6 @@ -72,5 +72,5 @@ <p> <!--<hr> -<center><h2>Examples of Use</h2></center> +<h2>Examples of Use</h2> <h3>Memcheck</h3> |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 14:31:25
|
CVS commit by nethercote: name index.html as home specifically, so that mirrors get the links right M +1 -1 menu.inc 1.12 --- devel-home/valgrind/menu.inc #1.11:1.12 @@ -3,5 +3,5 @@ <dl> <dt><b>About</b> -<dt><a href="/"> Home</a> +<dt><a href="index.html"> Home</a> <dt><a href="overview.html"> Overview</a> <dt><a href="tools.html"> Tools</a> |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 14:21:54
|
CVS commit by nethercote: minor fix M +1 -1 related.html 1.11 --- devel-home/valgrind/related.html #1.10:1.11 @@ -66,5 +66,5 @@ <ul> <li>FreeBSD: Doug Rabson has done a fairly complete port. See details in this - <a href="http://sourceforge.net/mailarchive/forum.php?thread_id=3660580&forum_id=12302"> + <a href="http://sourceforge.net/mailarchive/forum.php?thread_id=3660580&forum_id=12302"> mailing list thread</a>. We hope to integrate this port into Valgrind. <p> |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 14:17:10
|
CVS commit by nethercote: Remove bogus tag M +1 -1 users.html 1.38 --- devel-home/valgrind/users.html #1.37:1.38 @@ -252,5 +252,5 @@ <dt><a href="http://amarok.sourceforge.net/">amaroK</a> -<dd>A KDE media player.</a> +<dd>A KDE media player. <dt><a href="http://www.speex.org">Speex</a> |
|
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 |
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 11:59:01
|
CVS commit by nethercote:
Get url right
M +1 -1 related.html 1.9
--- devel-home/valgrind/related.html #1.8:1.9
@@ -21,5 +21,5 @@
<p>
<li>Jeremy Fitzhardinge has several Valgrind
- <a href="http://www.goop.org/~jeremy/valgrind/vgprof.html">patches</a>,
+ <a href="http://www.goop.org/~jeremy/valgrind/">patches</a>,
including one for vgprof, a Valgrind tool that does profiling like gprof,
but doesn't require recompilation, and works with threaded programs, and
|
|
From: Nicholas N. <nj...@ca...> - 2004-02-11 11:58:11
|
CVS commit by nethercote:
Make vgprof a bit clearer. Giving the skin the same name as the patched
version of gprof is very confusing...
M +5 -5 related.html 1.8
--- devel-home/valgrind/related.html #1.7:1.8
@@ -20,9 +20,9 @@
it collects.
<p>
-<li><a href="http://www.goop.org/~jeremy/valgrind/vgprof.html">VGProf</a>,
- by Jeremy Fitzhardinge, is a profiling tool like gprof, but doesn't
- require recompilation, and works with threaded programs, and can profile
- shared libraries. Jeremy also has various
- <a href="http://www.goop.org/~jeremy/valgrind/">patches</a> for Valgrind.
+<li>Jeremy Fitzhardinge has several Valgrind
+ <a href="http://www.goop.org/~jeremy/valgrind/vgprof.html">patches</a>,
+ including one for vgprof, a Valgrind tool that does profiling like gprof,
+ but doesn't require recompilation, and works with threaded programs, and
+ can profile shared libraries.
<p>
<li>Nick Nethercote has three experimental tools: a heap profiler, a
|
|
From: Marcel S. <mw...@re...> - 2004-02-11 07:35:20
|
On Wednesday 11 February 2004 08:23, Tom Hughes wrote: > In message <200...@re...> > > mw...@re... wrote: > > On Tuesday 10 February 2004 21:59, Tom Hughes wrote: > > > That gettid won't do anything useful as it will return the same value > > > in every thread which is most unlikely to be what the client program is > > > expecting to happen. > > > > Since i had a look at man 2 gettid and man 2 getpid it should behave like > > getpid. So i took the implementation of getpid and cloned it for gettid > > to get rid of messages telling me that syscall 224 isn't implemented. > > Not true, as getpid returns the PID of the first thread no matter which > thread it is called in while gettid returnd the PID of whichever thread > it is called in. > > The gettid manual does explain this: > > gettid returns the thread ID of the current process. This is equal to > the process ID (as returned by getpid(2)), unless the process is part > of a thread group (created by specifying the CLONE_THREAD flag to the > clone(2) system call). All processes in the same thread group have the > same PID, but each one has a unique TID. > > The problem is that under valgrind all the threads one in one kernel > level thread so the value returned by gettid will not vary with your > implementation. > > Tom Ok, understood. I will try another implementatiion and post it later on cu mws |
|
From: Tom H. <th...@cy...> - 2004-02-11 07:24:22
|
In message <200...@re...>
mw...@re... wrote:
> On Tuesday 10 February 2004 21:59, Tom Hughes wrote:
>
> > That gettid won't do anything useful as it will return the same value
> > in every thread which is most unlikely to be what the client program is
> > expecting to happen.
>
> Since i had a look at man 2 gettid and man 2 getpid it should behave like
> getpid. So i took the implementation of getpid and cloned it for gettid to
> get rid of messages telling me that syscall 224 isn't implemented.
Not true, as getpid returns the PID of the first thread no matter which
thread it is called in while gettid returnd the PID of whichever thread
it is called in.
The gettid manual does explain this:
gettid returns the thread ID of the current process. This is equal to
the process ID (as returned by getpid(2)), unless the process is part
of a thread group (created by specifying the CLONE_THREAD flag to the
clone(2) system call). All processes in the same thread group have the
same PID, but each one has a unique TID.
The problem is that under valgrind all the threads one in one kernel
level thread so the value returned by gettid will not vary with your
implementation.
Tom
--
Tom Hughes (th...@cy...)
Software Engineer, Cyberscience Corporation
http://www.cyberscience.com/
|
|
From: <mw...@re...> - 2004-02-11 07:17:27
|
On Tuesday 10 February 2004 21:59, Tom Hughes wrote: > In message <200...@re...> > > mw...@re... wrote: > > attached is a diff for the gettid syscall. > > That gettid won't do anything useful as it will return the same value > in every thread which is most unlikely to be what the client program is > expecting to happen. > > Tom Since i had a look at man 2 gettid and man 2 getpid it should behave like getpid. So i took the implementation of getpid and cloned it for gettid to get rid of messages telling me that syscall 224 isn't implemented. If this is wrong - you also must remove the getpid function - cause it is also senseless. Or am i wrong? cu mws |