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
(17) |
2
(15) |
3
(36) |
4
(24) |
5
(36) |
|
6
(18) |
7
(16) |
8
(18) |
9
(19) |
10
(18) |
11
(37) |
12
(18) |
|
13
(13) |
14
(21) |
15
(27) |
16
(10) |
17
(16) |
18
(25) |
19
(21) |
|
20
(11) |
21
(14) |
22
(6) |
23
(15) |
24
(27) |
25
(3) |
26
(9) |
|
27
(16) |
28
(24) |
29
(21) |
30
(43) |
31
(42) |
|
|
|
From: <sv...@va...> - 2005-03-24 14:13:58
|
Author: sewardj
Date: 2005-03-24 14:13:50 +0000 (Thu, 24 Mar 2005)
New Revision: 96
Modified:
trunk/info/developers.html
Log:
Third time lucky, perhaps.
Modified: trunk/info/developers.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/info/developers.html 2005-03-24 13:45:26 UTC (rev 95)
+++ trunk/info/developers.html 2005-03-24 14:13:50 UTC (rev 96)
@@ -57,6 +57,13 @@
</tr>
=20
<tr valign=3D"top">
+ <td><b>Dirk Mueller</b><br />
+ <a href=3D"mailto:dmu&#=
101;ll@gmx.net">d=
09;uell@gmx.net=
</a></td>
+ <td>Dirk contributed the malloc-free mismatch checking stuff and
+ various other bits and pieces, and acted as our KDE liaison.</td>
+</tr>
+
+<tr valign=3D"top">
<td><b>Julian Seward</b><br />
<?php echo vgemail('julian'); ?></td>
<td>Julian was the original designer and author of Valgrind,
@@ -72,14 +79,7 @@
tweakage.</td>
</tr>
=20
-<tr valign=3D"top">
- <td><b>Dirk Mueller</b><br />
- <a href=3D"mailto:dmu&#=
101;ll@gmx.net">d=
09;uell@gmx.net=
</a></td>
- <td>Dirk contributed the malloc-free mismatch checking stuff and
- various other bits and pieces, and acted as our KDE liaison.</td>
-</tr>
=20
-
<tr valign=3D"top"><td colspan=3D"2">
Frederic Gobry helped with autoconf and automake. Daniel Berlin modifie=
d
readelf's dwarf2 source line reader, written by Nick Clifton, for use=20
|
|
From: Julian S. <js...@ac...> - 2005-03-24 13:50:26
|
CVS commit by jseward: Add PaulM to this list. M +23 -15 ACKNOWLEDGEMENTS 1.3 --- valgrind/ACKNOWLEDGEMENTS #1.2:1.3 @@ -1,14 +1,3 @@ -Julian Seward, ju...@va... - -Julian was the original designer and author of Valgrind, created the -dynamic translation framework, wrote Memcheck and Addrcheck, and did -lots of other things. - -Nicholas Nethercote, nj...@va... - -Nick did the core/tool generalisation, wrote Cachegrind and Massif, -and tons of other stuff. - Jeremy Fitzhardinge, je...@va... @@ -21,9 +10,15 @@ more recent Linux/glibc versions. -Robert Walsh, rj...@va... +Nicholas Nethercote, nj...@va... -Robert added file descriptor leakage checking, new library -interception machinery, support for client allocation pools, and minor -other tweakage. +Nick did the core/tool generalisation, wrote Cachegrind and Massif, +and tons of other stuff. + +Paul Mackerras + +Paul did a lot of the initial per-architecture factoring that forms +the basis of the 3.0 line and is also to be seen in 2.4.0. He also did +UCode-based dynamic translation support for PowerPC, and created a set +of ppc-linux derivatives of the 2.X release line. Dirk Mueller, dm...@gm... @@ -36,4 +31,17 @@ Keeper of the very excellent http://www.valgrind.org. +Julian Seward, ju...@va... + +Julian was the original designer and author of Valgrind, created the +dynamic translation framework, wrote Memcheck and Addrcheck, and did +lots of other things. + +Robert Walsh, rj...@va... + +Robert added file descriptor leakage checking, new library +interception machinery, support for client allocation pools, and minor +other tweakage. + + Frederic Gobry helped with autoconf and automake. Daniel Berlin modified readelf's dwarf2 source line reader, written by Nick Clifton, |
|
From: <sv...@va...> - 2005-03-24 13:45:32
|
Author: sewardj
Date: 2005-03-24 13:45:26 +0000 (Thu, 24 Mar 2005)
New Revision: 95
Modified:
trunk/info/developers.html
Log:
Add PaulM as a person who did Significant Stuff.
Modified: trunk/info/developers.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/info/developers.html 2005-03-24 03:56:43 UTC (rev 94)
+++ trunk/info/developers.html 2005-03-24 13:45:26 UTC (rev 95)
@@ -18,21 +18,13 @@
</td></tr>
=20
<tr valign=3D"top">
- <td><b>Julian Seward</b><br />
- <?php echo vgemail('julian'); ?></td>
- <td>Julian was the original designer and author of Valgrind,
- created the dynamic translation framework, wrote Memcheck and
- Addrcheck, and did lots of other things.
+ <td><b>Cerion Armour-Brown</b><br />
+ <?php echo vgemail('cerion'); ?></td>
+ <td>Cerion has been working on PowerPC instruction set support
+ using the Vex dynamic-translation framework.</td>
</tr>
=20
<tr valign=3D"top">
- <td><b>Nicholas Nethercote</b><br />
- <?php echo vgemail('nick'); ?></td>
- <td>Nick did the core/tool generalisation, wrote Cachegrind
- and Massif, and tons of other stuff.</td>
-</tr>
-
-<tr valign=3D"top">
<td><b>Jeremy Fitzhardinge</b><br />
<?php echo vgemail('jeremy'); ?></td>
<td>Jeremy wrote Helgrind and totally overhauled low-level
@@ -48,6 +40,31 @@
</tr>
=20
<tr valign=3D"top">
+ <td><b>Nicholas Nethercote</b><br />
+ <?php echo vgemail('nick'); ?></td>
+ <td>Nick did the core/tool generalisation, wrote Cachegrind
+ and Massif, and tons of other stuff.</td>
+</tr>
+
+<tr valign=3D"top">
+ <td><b>Paul Mackerras</b><br />
+ </td>
+ <td>Paul did a lot of the initial per-architecture factoring that
+ forms the basis of the 3.0 line and is also to be seen in 2.4.0.
+ He also did UCode-based dynamic translation support for PowerPC,
+ and created a set of ppc-linux derivatives of the 2.X release
+ line.</td>
+</tr>
+
+<tr valign=3D"top">
+ <td><b>Julian Seward</b><br />
+ <?php echo vgemail('julian'); ?></td>
+ <td>Julian was the original designer and author of Valgrind,
+ created the dynamic translation frameworks, wrote Memcheck and
+ Addrcheck, and did lots of other things.
+</tr>
+
+<tr valign=3D"top">
<td><b>Robert Walsh</b><br />
<?php echo vgemail('robert'); ?></td>
<td>Robert added file descriptor leakage checking, new library intercep=
tion
@@ -62,12 +79,6 @@
various other bits and pieces, and acted as our KDE liaison.</td>
</tr>
=20
-<tr valign=3D"top">
- <td><b>Cerion Armour-Brown</b><br />
- <?php echo vgemail('cerion'); ?></td>
- <td>Cerion has been working on PowerPC instruction set support
- using the Vex dynamic-translation framework.</td>
-</tr>
=20
<tr valign=3D"top"><td colspan=3D"2">
Frederic Gobry helped with autoconf and automake. Daniel Berlin modifie=
d
|
|
From: Jeremy F. <je...@go...> - 2005-03-24 05:55:40
|
Julian Seward wrote:
>Yes, in particular, many thanks to Jeremy for working hard on
>threading 'n' stuff, and being the 2.4 release coordinator.
>
Now we get to see how urgent the 2.4.1 release is...
J
|
|
From: Julian S. <js...@ac...> - 2005-03-24 05:03:39
|
> Three cheers for Jeremy's and Julian's hard work in getting this release > out! Yes, in particular, many thanks to Jeremy for working hard on threading 'n' stuff, and being the 2.4 release coordinator. J |
|
From: Nicholas N. <nj...@cs...> - 2005-03-24 04:54:10
|
On Thu, 24 Mar 2005, Julian Seward wrote: > I've tagged the cvs tree with VALGRIND_2_4_0. This is not a branch > tag since the entire cvs repo is now a branch. 2.4.0 is released > and www.valgrind.org is duly updated. Three cheers for Jeremy's and Julian's hard work in getting this release out! N |
|
From: Julian S. <js...@ac...> - 2005-03-24 04:42:12
|
I've tagged the cvs tree with VALGRIND_2_4_0. This is not a branch tag since the entire cvs repo is now a branch. 2.4.0 is released and www.valgrind.org is duly updated. J |
|
From: Julian S. <js...@ac...> - 2005-03-24 04:39:51
|
We are pleased to announce a new stable release of Valgrind, version 2.4.0. It is available from http://www.valgrind.org. Valgrind is an award-winning open-source tool suite for debugging and profiling x86-Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, avoiding hours of frustrating bug-hunting, and make your code more stable. You can also perform detailed time and space profiling to help speed up and slim down your programs. 2.4.0 brings six months worth of improvements and bug fixes. We believe it to be a worthy successor to the previous stable release, 2.2.0. There are dozens of bug fixes and minor improvements. There are also some major user-visible changes. A full list is shown below. 2.4.X will be the last x86-only Valgrind. Future releases (3.0 and above) will be built on a new dynamic-translation framework capable of supporting a range of processor architectures. Our first port away from x86 will be Valgrind for AMD64-Linux. Finally, Valgrind has a new home: http://www.valgrind.org. A big thank-you to the KDE folks who have generously provided hosting, repository and bugzilla support over the past three years. Happy (and productive) debugging and profiling, -- The Valgrind developers Stable release 2.4.0 (March 2005) -- CHANGES RELATIVE TO 2.2.0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2.4.0 brings many significant changes and bug fixes. The most significant user-visible change is that we no longer supply our own pthread implementation. Instead, Valgrind is finally capable of running the native thread library, either LinuxThreads or NPTL. This means our libpthread has gone, along with the bugs associated with it. Valgrind now supports the kernel's threading syscalls, and lets you use your standard system libpthread. As a result: * There are many fewer system dependencies and strange library-related bugs. There is a small performance improvement, and a large stability improvement. * On the downside, Valgrind can no longer report misuses of the POSIX PThreads API. It also means that Helgrind currently does not work. We hope to fix these problems in a future release. Note that running the native thread libraries does not mean Valgrind is able to provide genuine concurrent execution on SMPs. We still impose the restriction that only one thread is running at any given time. There are many other significant changes too: * Memcheck is (once again) the default tool. * The default stack backtrace is now 12 call frames, rather than 4. * Suppressions can have up to 25 call frame matches, rather than 4. * Memcheck and Addrcheck use less memory. Under some circumstances, they no longer allocate shadow memory if there are large regions of memory with the same A/V states - such as an mmaped file. * The memory-leak detector in Memcheck and Addrcheck has been improved. It now reports more types of memory leak, including leaked cycles. When reporting leaked memory, it can distinguish between directly leaked memory (memory with no references), and indirectly leaked memory (memory only referred to by other leaked memory). * Memcheck's confusion over the effect of mprotect() has been fixed: previously mprotect could erroneously mark undefined data as defined. * Signal handling is much improved and should be very close to what you get when running natively. One result of this is that Valgrind observes changes to sigcontexts passed to signal handlers. Such modifications will take effect when the signal returns. You will need to run with --single-step=yes to make this useful. * Valgrind is built in Position Independent Executable (PIE) format if your toolchain supports it. This allows it to take advantage of all the available address space on systems with 4Gbyte user address spaces. * Valgrind can now run itself (requires PIE support). * Syscall arguments are now checked for validity. Previously all memory used by syscalls was checked, but now the actual values passed are also checked. * Syscall wrappers are more robust against bad addresses being passed to syscalls: they will fail with EFAULT rather than killing Valgrind with SIGSEGV. * Because clone() is directly supported, some non-pthread uses of it will work. Partial sharing (where some resources are shared, and some are not) is not supported. * open() and readlink() on /proc/self/exe are supported. BUGS FIXED: 88520 pipe+fork+dup2 kills the main program 88604 Valgrind Aborts when using $VALGRIND_OPTS and user progra... 88614 valgrind: vg_libpthread.c:2323 (read): Assertion `read_pt... 88703 Stabs parser fails to handle ";" 88886 ioctl wrappers for TIOCMBIS and TIOCMBIC 89032 valgrind pthread_cond_timedwait fails 89106 the 'impossible' happened 89139 Missing sched_setaffinity & sched_getaffinity 89198 valgrind lacks support for SIOCSPGRP and SIOCGPGRP 89263 Missing ioctl translations for scsi-generic and CD playing 89440 tests/deadlock.c line endings 89481 `impossible' happened: EXEC FAILED 89663 valgrind 2.2.0 crash on Redhat 7.2 89792 Report pthread_mutex_lock() deadlocks instead of returnin... 90111 statvfs64 gives invalid error/warning 90128 crash+memory fault with stabs generated by gnat for a run... 90778 VALGRIND_CHECK_DEFINED() not as documented in memcheck.h 90834 cachegrind crashes at end of program without reporting re... 91028 valgrind: vg_memory.c:229 (vgPlain_unmap_range): Assertio... 91162 valgrind crash while debugging drivel 1.2.1 91199 Unimplemented function 91325 Signal routing does not propagate the siginfo structure 91599 Assertion `cv == ((void *)0)' 91604 rw_lookup clears orig and sends the NULL value to rw_new 91821 Small problems building valgrind with $top_builddir ne $t... 91844 signal 11 (SIGSEGV) at get_tcb (libpthread.c:86) in corec... 92264 UNIMPLEMENTED FUNCTION: pthread_condattr_setpshared 92331 per-target flags necessitate AM_PROG_CC_C_O 92420 valgrind doesn't compile with linux 2.6.8.1/9 92513 Valgrind 2.2.0 generates some warning messages 92528 vg_symtab2.c:170 (addLoc): Assertion `loc->size > 0' failed. 93096 unhandled ioctl 0x4B3A and 0x5601 93117 Tool and core interface versions do not match 93128 Can't run valgrind --tool=memcheck because of unimplement... 93174 Valgrind can crash if passed bad args to certain syscalls 93309 Stack frame in new thread is badly aligned 93328 Wrong types used with sys_sigprocmask() 93763 /usr/include/asm/msr.h is missing 93776 valgrind: vg_memory.c:508 (vgPlain_find_map_space): Asser... 93810 fcntl() argument checking a bit too strict 94378 Assertion `tst->sigqueue_head != tst->sigqueue_tail' failed. 94429 valgrind 2.2.0 segfault with mmap64 in glibc 2.3.3 94645 Impossible happened: PINSRW mem 94953 valgrind: the `impossible' happened: SIGSEGV 95667 Valgrind does not work with any KDE app 96243 Assertion 'res==0' failed 96252 stage2 loader of valgrind fails to allocate memory 96520 All programs crashing at _dl_start (in /lib/ld-2.3.3.so) ... 96660 ioctl CDROMREADTOCENTRY causes bogus warnings 96747 After looping in a segfault handler, the impossible happens 96923 Zero sized arrays crash valgrind trace back with SIGFPE 96948 valgrind stops with assertion failure regarding mmap2 96966 valgrind fails when application opens more than 16 sockets 97398 valgrind: vg_libpthread.c:2667 Assertion failed 97407 valgrind: vg_mylibc.c:1226 (vgPlain_safe_fd): Assertion `... 97427 "Warning: invalid file descriptor -1 in syscall close()" ... 97785 missing backtrace 97792 build in obj dir fails - autoconf / makefile cleanup 97880 pthread_mutex_lock fails from shared library (special ker... 97975 program aborts without ang VG messages 98129 Failed when open and close file 230000 times using stdio 98175 Crashes when using valgrind-2.2.0 with a program using al... 98288 Massif broken 98303 UNIMPLEMENTED FUNCTION pthread_condattr_setpshared 98630 failed--compilation missing warnings.pm, fails to make he... 98756 Cannot valgrind signal-heavy kdrive X server 98966 valgrinding the JVM fails with a sanity check assertion 99035 Valgrind crashes while profiling 99142 loops with message "Signal 11 being dropped from thread 0... 99195 threaded apps crash on thread start (using QThread::start... 99348 Assertion `vgPlain_lseek(core_fd, 0, 1) == phdrs[i].p_off... 99568 False negative due to mishandling of mprotect 99738 valgrind memcheck crashes on program that uses sigitimer 99923 0-sized allocations are reported as leaks 99949 program seg faults after exit() 100036 "newSuperblock's request for 1048576 bytes failed" 100116 valgrind: (pthread_cond_init): Assertion `sizeof(* cond) ... 100486 memcheck reports "valgrind: the `impossible' happened: V... 100833 second call to "mremap" fails with EINVAL 101156 (vgPlain_find_map_space): Assertion `(addr & ((1 << 12)-1... 101173 Assertion `recDepth >= 0 && recDepth < 500' failed 101291 creating threads in a forked process fails 101313 valgrind causes different behavior when resizing a window... 101423 segfault for c++ array of floats 101562 valgrind massif dies on SIGINT even with signal handler r... |
|
From: <js...@ac...> - 2005-03-24 04:04:44
|
Nightly build on phoenix ( SuSE 9.1 ) started at 2005-03-24 03:50:00 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_mmx: valgrind ./insn_mmx insn_mmxext: (skipping, prereq failed: ../../../tests/cputest x86-mmxext) insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 201 tests, 5 stderr failures, 0 stdout failures ================= memcheck/tests/pth_once (stderr) memcheck/tests/scalar (stderr) memcheck/tests/threadederrno (stderr) memcheck/tests/writev (stderr) corecheck/tests/fdleak_fcntl (stderr) make: *** [regtest] Error 1 |
|
From: <sv...@va...> - 2005-03-24 03:56:48
|
Author: sewardj Date: 2005-03-24 03:56:43 +0000 (Thu, 24 Mar 2005) New Revision: 94 Modified: trunk/devel/cvs_svn.html Log: Update dev line status a bit. Modified: trunk/devel/cvs_svn.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/devel/cvs_svn.html 2005-03-24 03:43:09 UTC (rev 93) +++ trunk/devel/cvs_svn.html 2005-03-24 03:56:43 UTC (rev 94) @@ -55,9 +55,15 @@ <code> make install</code><br /> </p> =20 -<p><b>Note:</b> as of mid March 2005, the 3.0 line has seen massive -upheaval and so is majorly broken in various ways. We expect -this will improve rapidly. For the time being, however, don't -bother to check it out unless you are a die-hard developer and -are prepared for serious breakage.</p> +<p><b>Note:</b> as of late March 2005, the 3.0 line has seen massive +upheaval. It builds and works pretty well on x86-linux and is +eminently usable. In some ways is already better than the current +stable 2.4.0 release, mostly in its handling of SSE/SSE2 code. +</p> =20 +<p>On amd64-linux it is just coming to life, but is majorly broken in +various ways, and is not usable for anything useful yet. We expect +this will improve rapidly. For the time being, however, don't bother +to try building on amd64-linux unless you are a die-hard developer and +are prepared for serious breakage. +</p> |
|
From: <sv...@va...> - 2005-03-24 03:43:15
|
Author: sewardj Date: 2005-03-24 03:43:09 +0000 (Thu, 24 Mar 2005) New Revision: 93 Added: trunk/downloads/valgrind-2.4.0.tar.bz2 Removed: trunk/valgrind-2.4.0.tar.bz2 Log: Move this file to the right place. Duh. Copied: trunk/downloads/valgrind-2.4.0.tar.bz2 (from rev 91, trunk/valgri= nd-2.4.0.tar.bz2) Deleted: trunk/valgrind-2.4.0.tar.bz2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (Binary files differ) |
|
From: <sv...@va...> - 2005-03-24 03:42:44
|
Author: sewardj Date: 2005-03-24 03:42:41 +0000 (Thu, 24 Mar 2005) New Revision: 92 Modified: trunk/downloads/source_code.html Log: * Fix the 2.4.0 wording a bit more. * Get rid of the Limitations section; it was very out-of-date. Modified: trunk/downloads/source_code.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/downloads/source_code.html 2005-03-24 03:36:31 UTC (rev 91) +++ trunk/downloads/source_code.html 2005-03-24 03:42:41 UTC (rev 92) @@ -29,11 +29,12 @@ <span class=3D"md5sum">md5: 1d0bd81d368789946d32d18a468ea0cf</span> </p> =20 -<p>Compared to the 2.2.0 stable release, 2.4.0 has much improved +<p>Compared to the 2.2.0 stable release, 2.4.0 has improved signals/syscalls/threads support, works well on recent Linux distros, -and reduced memory consumption running Memcheck/Addrcheck. There are -many other improvements and refinements, and dozens of bug fixes, -listed in the NEWS file.</p> +has reduced memory consumption running Memcheck/Addrcheck, and has +better memory-leak detection. There are many other improvements and +refinements, and dozens of bug fixes, listed in the NEWS file. +</p> =20 <p>2.4.0 builds and runs its regression tests on: Red Hat 7.3, Fedora Core 3, SuSE 9.1 and 9.2. We believe it should @@ -67,30 +68,9 @@ =20 <h3>System Requirements</h3> =20 -<p>Programs running under Valgrind run significantly more slowly, -and use much more memory -- e.g. more than twice as much as -normal under the Memcheck tool. Therefore, it's best to have a -machine that runs your normal applications very comfortably.</p> +<p>Programs running under Valgrind run significantly more slowly, and +use much more memory -- e.g. more than twice as much as normal under +the Memcheck tool. Therefore, it's best to use Valgrind on the most +capable machine you can get your hands on. +</p> =20 - - -<h3>Limitations</h3> - -<p>The <a href=3D"/docs/manual/manual.html">manual</a> contains a -complete list of=20 -<a href=3D"/docs/manual/coregrind_core.html#limits">limitations</a>,=20 -the most significant of which are:</p> - -<ul> - <li>Incomplete support for SIMD instructions. 2.0.0 has complete - 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> - <li>Support for non-POSIX signal stuff is flaky. If you stick to - POSIX signals you should be ok.</li> -</ul> - - -<p>As always, the <a href=3D"/docs/manual/manual.html">manual</a> -is the source of all detailed info.</p> - |
|
From: Nicholas N. <nj...@cs...> - 2005-03-24 03:37:30
|
On Wed, 23 Mar 2005, Jeremy Fitzhardinge wrote: > I think there's some more scope for factoring out the secondary map > code. Pretty much all the tools which have shadow memory copy > memcheck's primary/secondary map code; it would be nice if they could > share this in some way. I've tried to factor out this commonality before, and failed. I'd love to see someone else succeed at it. N |
|
From: <sv...@va...> - 2005-03-24 03:36:40
|
Author: sewardj Date: 2005-03-24 03:36:31 +0000 (Thu, 24 Mar 2005) New Revision: 91 Added: trunk/downloads/archive/valgrind-2.2.0.tar.bz2 trunk/valgrind-2.4.0.tar.bz2 Removed: trunk/downloads/valgrind-2.2.0.tar.bz2 Modified: trunk/downloads/archive.html trunk/downloads/source_code.html trunk/index.html trunk/info/news.html trunk/php/.htconfx Log: Update for 2.4.0. Copied: trunk/downloads/archive/valgrind-2.2.0.tar.bz2 (from rev 90, trun= k/downloads/valgrind-2.2.0.tar.bz2) Modified: trunk/downloads/archive.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/downloads/archive.html 2005-03-18 17:00:21 UTC (rev 90) +++ trunk/downloads/archive.html 2005-03-24 03:36:31 UTC (rev 91) @@ -13,7 +13,32 @@ <div id=3D"release"> =20 =20 + <div class=3D"hr_brown"><hr/></div> +<h3>valgrind-2.2.0</h3> + +<p> +<a href=3D"/downloads/archive/valgrind-2.2.0.tar.bz2">valgrind 2.2.0 (ta= r.bz2)</a> +[965Kb] - Aug 31 2004<br /> +<span class=3D"md5sum">md5: 30dc51f6fc94751b90b04af9c2e2c656</span> +</p> + +<p>Compared to the 2.0.0. stable release, 2.2.0 has much improved +signals/syscalls/threads support, works well on recent Linux +distros, improves SSE2/SSE3 support, and brings you Massif, a new +tool for investigating space use of your programs. There are +literally dozens of other improvements and refinements, and +hundreds of bug fixes, listed in the NEWS file.</p> + +<p>2.2.0 builds and runs its regression tests on: Red Hat 7.2, +7.3, 8.0, 9, Fedora Core 2, and SuSE 9.1. We believe it should +work on Linux distributions with kernel 2.4 or 2.6 and glibc +2.2.X or 2.3.X.</p> + + + + +<div class=3D"hr_brown"><hr/></div> <h3>valgrind 2.1.1</h3> =20 <p> Modified: trunk/downloads/source_code.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/downloads/source_code.html 2005-03-18 17:00:21 UTC (rev 90) +++ trunk/downloads/source_code.html 2005-03-24 03:36:31 UTC (rev 91) @@ -24,20 +24,19 @@ <h3>Current Stable Release:</h3> =20 <p> -<a href=3D"/downloads/valgrind-2.2.0.tar.bz2">valgrind 2.2.0 (tar.bz2)</= a>=20 -[965Kb] - Aug 31 2004<br /> -<span class=3D"md5sum">md5: 30dc51f6fc94751b90b04af9c2e2c656</span> +<a href=3D"/downloads/valgrind-2.4.0.tar.bz2">valgrind 2.4.0 (tar.bz2)</= a>=20 +[1072Kb] - March 24 2005<br /> +<span class=3D"md5sum">md5: 1d0bd81d368789946d32d18a468ea0cf</span> </p> =20 -<p>Compared to the 2.0.0. stable release, 2.2.0 has much improved -signals/syscalls/threads support, works well on recent Linux -distros, improves SSE2/SSE3 support, and brings you Massif, a new -tool for investigating space use of your programs. There are -literally dozens of other improvements and refinements, and -hundreds of bug fixes, listed in the NEWS file.</p> +<p>Compared to the 2.2.0 stable release, 2.4.0 has much improved +signals/syscalls/threads support, works well on recent Linux distros, +and reduced memory consumption running Memcheck/Addrcheck. There are +many other improvements and refinements, and dozens of bug fixes, +listed in the NEWS file.</p> =20 -<p>2.2.0 builds and runs its regression tests on: Red Hat 7.2, -7.3, 8.0, 9, Fedora Core 2, and SuSE 9.1. We believe it should +<p>2.4.0 builds and runs its regression tests on: Red Hat 7.3, +Fedora Core 3, SuSE 9.1 and 9.2. We believe it should work on Linux distributions with kernel 2.4 or 2.6 and glibc 2.2.X or 2.3.X.</p> =20 @@ -46,7 +45,7 @@ <a name=3D"current-devel"></a> <h3>Current Developer Release: </h3> =20 -<p>2.2.0 supersedes all previous releases, and so there is +<p>2.4.0 supersedes all previous releases, and so there is currently no development release available.</p> =20 =20 Deleted: trunk/downloads/valgrind-2.2.0.tar.bz2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (Binary files differ) Modified: trunk/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/index.html 2005-03-18 17:00:21 UTC (rev 90) +++ trunk/index.html 2005-03-24 03:36:31 UTC (rev 91) @@ -38,6 +38,9 @@ =20 <ul> =20 + <li><p>March 24, 2005: A new stable version, 2.4.0, is + available.</p></li> + <li><p>March 12, 2005: The Valgrind website has been overhauled, and moved to <a href=3D"http://www.valgrind.org">www.valgrind.org</a>. Many thanks to KDE for hosting the previous website.</p></li> Modified: trunk/info/news.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/info/news.html 2005-03-18 17:00:21 UTC (rev 90) +++ trunk/info/news.html 2005-03-24 03:36:31 UTC (rev 91) @@ -7,6 +7,12 @@ =20 <ul> =20 + <li><p>March 24, 2005:<br /> A new stable release,=20 + <a href=3D"/downloads/source_code.html#current-stable">valgrind + 2.4.0</a>, is available. Relative to 2.2.0, 2.4.0 has + improved thread and signal support, reduced memory consumption, + and dozens of bug fixes.</p></li> + <li><p>August 31, 2004:<br /> A new stable release,=20 <a href=3D"/downloads/source_code.html#current-stable">valgrind 2.2.0</a>, is available. 2.2.0 brings many improvements over Modified: trunk/php/.htconfx =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/php/.htconfx 2005-03-18 17:00:21 UTC (rev 90) +++ trunk/php/.htconfx 2005-03-24 03:36:31 UTC (rev 91) @@ -26,8 +26,8 @@ 'dt_copyright' =3D> '2000-2005 ', =20 /* current release info */ - 'release-date' =3D> 'Aug 31 2004', - 'release-version' =3D> 'valgrind-2.2.0', + 'release-date' =3D> 'March 24 2005', + 'release-version' =3D> 'valgrind-2.4.0', =20 /* mailing lists, bug reports, etc. */ 'vgannounce' =3D> array(=20 Added: trunk/valgrind-2.4.0.tar.bz2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D (Binary files differ) Property changes on: trunk/valgrind-2.4.0.tar.bz2 ___________________________________________________________________ Name: svn:mime-type + application/octet-stream |
|
From: Tom H. <to...@co...> - 2005-03-24 03:28:28
|
Nightly build on dunsmere ( Fedora Core 3 ) started at 2005-03-24 03:20:03 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_cmov: valgrind ./insn_cmov insn_fpu: valgrind ./insn_fpu insn_mmx: valgrind ./insn_mmx insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int sh: line 1: 31615 Segmentation fault VALGRINDLIB=/tmp/valgrind.6502/valgrind/.in_place /tmp/valgrind.6502/valgrind/./coregrind/valgrind --command-line-only=yes --memcheck:leak-check=no --addrcheck:leak-check=no --tool=none ./int >int.stdout.out 2>int.stderr.out pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 207 tests, 2 stderr failures, 0 stdout failures ================= memcheck/tests/scalar (stderr) memcheck/tests/scalar_supp (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-24 03:22:26
|
Nightly build on audi ( Red Hat 9 ) started at 2005-03-24 03:15:02 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow fpu_lazy_eflags: valgrind ./fpu_lazy_eflags insn_basic: valgrind ./insn_basic insn_cmov: valgrind ./insn_cmov insn_fpu: valgrind ./insn_fpu insn_mmx: valgrind ./insn_mmx insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 206 tests, 1 stderr failure, 0 stdout failures ================= memcheck/tests/scalar (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-24 03:16:30
|
Nightly build on ginetta ( Red Hat 8.0 ) started at 2005-03-24 03:10:01 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_cmov: valgrind ./insn_cmov insn_fpu: valgrind ./insn_fpu insn_mmx: valgrind ./insn_mmx insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 205 tests, 3 stderr failures, 0 stdout failures ================= memcheck/tests/pth_once (stderr) memcheck/tests/scalar (stderr) memcheck/tests/threadederrno (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-24 03:15:33
|
Nightly build on standard ( Red Hat 7.2 ) started at 2005-03-24 03:00:02 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow insn_mmxext: valgrind ./insn_mmxext insn_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int pushpopseg: valgrind ./pushpopseg rcl_assert: valgrind ./rcl_assert seg_override: valgrind ./seg_override -- Finished tests in none/tests/x86 ------------------------------------ yield: valgrind ./yield -- Finished tests in none/tests ---------------------------------------- == 205 tests, 6 stderr failures, 0 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pth_once (stderr) memcheck/tests/scalar (stderr) memcheck/tests/threadederrno (stderr) memcheck/tests/vgtest_ume (stderr) addrcheck/tests/leak-tree (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-24 03:11:45
|
Nightly build on alvis ( Red Hat 7.3 ) started at 2005-03-24 03:05:01 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow == 205 tests, 17 stderr failures, 0 stdout failures ================= memcheck/tests/addressable (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/distinguished-writes (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/pth_once (stderr) memcheck/tests/scalar (stderr) memcheck/tests/threadederrno (stderr) memcheck/tests/vgtest_ume (stderr) addrcheck/tests/leak-0 (stderr) addrcheck/tests/leak-cycle (stderr) addrcheck/tests/leak-regroot (stderr) addrcheck/tests/leak-tree (stderr) make: *** [regtest] Error 1 |
|
From: Jeremy F. <je...@go...> - 2005-03-24 02:55:37
|
Nicholas Nethercote wrote:
> This is important, especially with the address space layout problems
> we still sometimes have. If we can get Memcheck's memory usage down
> as we've discussed, then I think we should do something like this.
I think there's some more scope for factoring out the secondary map
code. Pretty much all the tools which have shadow memory copy
memcheck's primary/secondary map code; it would be nice if they could
share this in some way.
J
|
|
From: Nicholas N. <nj...@cs...> - 2005-03-24 02:31:40
|
On Wed, 23 Mar 2005, Julian Seward wrote: > * The real killer is that I bet practically nobody uses Addrcheck. > Memcheck tells us everything Addrcheck does, and much more > besides. The December 2003 survey pegged Addrcheck usage at about 6% of all usage. Memcheck was at 85%. The surveys I've receved then (about 15) indicate pretty similar usage levels. N |
|
From: Julian S. <js...@ac...> - 2005-03-24 02:29:55
|
CVS commit by jseward: --> 2.4.0 M +1 -1 configure.in 1.155 --- valgrind/configure.in #1.154:1.155 @@ -1,4 +1,4 @@ # Process this file with autoconf to produce a configure script. -AC_INIT(Valgrind, 2.4.0.rc4, val...@li...) +AC_INIT(Valgrind, 2.4.0, val...@li...) AC_CONFIG_SRCDIR(coregrind/vg_main.c) AM_CONFIG_HEADER(config.h) |
|
From: Nicholas N. <nj...@cs...> - 2005-03-24 02:29:52
|
On Wed, 23 Mar 2005, Oswald Buddenhagen wrote: > taking this to the extreme, possibly close-to-impossible: would it be > possible to create a(n efficient) tool stacking architecture? this would > sort of resolve the addrcheck vs. memcheck question (by making memcheck > addrcheck + initcheck). this might also be interesting in conjunction > with "unrelated" tools, as sometimes there are correlations between bugs > of different classes. Possible? Probably. I deliberately didn't design for this possibility when I did the core/tool modularisation because the cost/benefit ratio would be really high. N |
|
From: Julian S. <js...@ac...> - 2005-03-24 02:29:03
|
CVS commit by jseward: Fix 'make distcheck'. M +1 -1 Makefile.am 1.25 --- valgrind/coregrind/x86/Makefile.am #1.24:1.25 @@ -18,5 +18,5 @@ BUILT_SOURCES = stage2.lds core_arch_asm_offsets.h -CLEANFILES = stage2.lds core_arch_asm_offsets.h +CLEANFILES = stage2.lds core_arch_asm_offsets.h core_arch_asm_offsets.h.dist libarch_a_SOURCES = \ |
|
From: Nicholas N. <nj...@cs...> - 2005-03-24 02:09:52
|
On Wed, 23 Mar 2005, Robert Walsh wrote: > Could addrcheck and memcheck be rolled into one? In other words, a > "quiet" version of memcheck that produces only what reports addrcheck > would produce? I like this idea. But I think the key thing is that currently Addrcheck uses much less address space than Memcheck. Indeed, most of the Addrcheck-only code deals with the differently laid-out secondary maps. This is important, especially with the address space layout problems we still sometimes have. If we can get Memcheck's memory usage down as we've discussed, then I think we should do something like this. N |