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: Jeremy F. <je...@go...> - 2005-03-05 23:32:02
|
Bryan O'Sullivan wrote:
>FWIW, SuSE puts docs in /usr/share/doc/packages. You should probably
>use %{_docdir} instead of an absolute path here, which will work
>correctly on both SuSE and RH RPM versions.
>
>
Ah, OK. But the Makefiles also need to install them in the right
place. Do you know what the corresponding auto* magic is?
J
|
|
From: Bryan O'S. <bo...@se...> - 2005-03-05 22:40:54
|
On Sat, 2005-03-05 at 03:02 +0100, Jeremy Fitzhardinge wrote:
> --- valgrind/valgrind.spec.in #1.20:1.21
> @@ -3,4 +3,5 @@
> Version: @VERSION@
> Release: 1
> +Epoch: 2
> Copyright: GPL
> Group: Development/Debuggers
> @@ -52,5 +53,5 @@
>
> %doc
> -/usr/share/doc/valgrind/*
> +/usr/share/doc/valgrind-@VERSION@/*
>
> %clean
FWIW, SuSE puts docs in /usr/share/doc/packages. You should probably
use %{_docdir} instead of an absolute path here, which will work
correctly on both SuSE and RH RPM versions.
<b
--
Bryan O'Sullivan <bo...@se...>
|
|
From: Robert W. <rj...@du...> - 2005-03-05 22:06:37
|
CVS commit by rjwalsh: Work in progress on the valgrind manual page. This hasn't been content or copy edited yet, and a lot of stuff is just placeholders. I hope to finish it this evening - I have an errand to run right now. A valgrind.1 1.1 M +1 -0 Makefile.am 1.6 --- valgrind/docs/Makefile.am #1.5:1.6 @@ -2,2 +2,3 @@ dist_doc_DATA = manual.html +dist_man_MANS = valgrind.1 |
|
From: Robert W. <rj...@du...> - 2005-03-05 22:03:41
|
CVS commit by rjwalsh:
Fix cmdline tests for match new --num-callers stuff.
M +1 -1 cmdline1.stdout.exp 1.14
M +1 -1 cmdline2.stdout.exp 1.16
--- valgrind/none/tests/cmdline1.stdout.exp #1.13:1.14
@@ -22,5 +22,5 @@
--log-socket=ipaddr:port log messages to socket ipaddr:port
--demangle=no|yes automatically demangle C++ names? [yes]
- --num-callers=<number> show <num> callers in stack traces [4]
+ --num-callers=<number> show <num> callers in stack traces [12]
--error-limit=no|yes stop showing new errors if too many? [yes]
--show-below-main=no|yes continue stack traces below main() [no]
--- valgrind/none/tests/cmdline2.stdout.exp #1.15:1.16
@@ -22,5 +22,5 @@
--log-socket=ipaddr:port log messages to socket ipaddr:port
--demangle=no|yes automatically demangle C++ names? [yes]
- --num-callers=<number> show <num> callers in stack traces [4]
+ --num-callers=<number> show <num> callers in stack traces [12]
--error-limit=no|yes stop showing new errors if too many? [yes]
--show-below-main=no|yes continue stack traces below main() [no]
|
|
From: Jeremy F. <je...@go...> - 2005-03-05 20:36:03
|
Nicholas Nethercote wrote:
> Julian said:
>
> Ok. I change my vote. Let's have --leak-check=yes|summary|no,
> with the default being yes, and summary ... well, just producing
> a summary. When =yes is in effect, we should also print a line
> saying "use ...=summary or ...=no to reduce the amount of output."
>
Well, in use over the last few days, I've found --leak-check=summary is
the most useful default. It tells you whether there are definite leaks,
and suggests using --leak-check=full to see the details.
My preference would be to make it the default, and change the test
scripts to use --leak-check=no to save on having to fiddle all the .exp
files.
J
|
|
From: Robert W. <rj...@du...> - 2005-03-05 19:48:07
|
CVS commit by rjwalsh: --num-callers default is now 12, so say that in the help. M +1 -1 vg_main.c 1.262 --- valgrind/coregrind/vg_main.c #1.261:1.262 @@ -1487,5 +1487,5 @@ void usage ( Bool debug_help ) " --log-socket=ipaddr:port log messages to socket ipaddr:port\n" " --demangle=no|yes automatically demangle C++ names? [yes]\n" -" --num-callers=<number> show <num> callers in stack traces [4]\n" +" --num-callers=<number> show <num> callers in stack traces [12]\n" " --error-limit=no|yes stop showing new errors if too many? [yes]\n" " --show-below-main=no|yes continue stack traces below main() [no]\n" |
|
From: Oswald B. <os...@kd...> - 2005-03-05 19:21:53
|
On Sat, Mar 05, 2005 at 04:02:19PM +0000, Julian Seward wrote: > We'll have to keep the 2.4 line alive for a while, probably in kde's > cvs, so we can put critical bug fixes on it. > are you aware of the fact that the migration of kde's cvs to svn is a matter of a few weeks according to the current plan? -- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! -- Chaos, panic, and disorder - my work here is done. |
|
From: Tom H. <th...@cy...> - 2005-03-05 16:55:47
|
CVS commit by thughes: Update some .cvsignore files. M +2 -0 memcheck/tests/.cvsignore 1.34 M +1 -0 none/tests/.cvsignore 1.27 --- valgrind/memcheck/tests/.cvsignore #1.33:1.34 @@ -15,4 +15,5 @@ clientstackperm custom_alloc +describe-block dir doublefree @@ -33,4 +34,5 @@ leak-regroot leak-tree +leakotron malloc1 malloc2 --- valgrind/none/tests/.cvsignore #1.26:1.27 @@ -32,4 +32,5 @@ insn_sse2 insn_sse2.c +manythreads map_unmap mq |
|
From: Julian S. <js...@ac...> - 2005-03-05 16:02:32
|
> > If the Vex-mainline merge commit happens before the CVS migration, we'll > > end up with broken history. > > Broken history will be hard to avoid, to at least some extent -- either > the post-split CVS history will be lost, or the post-split SVN history > will be lost. (The SVN tree has the pre-split history, since it was > imported from CVS.) s/hard/impossible/g History is nice to have, but it's not critical. If there are any critical history items on the cvs trail that ought to be kept, we can post-hoc modify the svn log entries if needed. I'm not going to go to major effort to maintain/merge precise history. I've never found it terribly useful. If I wanted to spend an extra chunk of time in this process, it'd be more useful to write some top level overviews for some of our critical but underdocumented subsystems. Those sorts of overviews would have saved me many hours recently, and they make it easier for newcomers to contribute usefully. Currently our barrier to entry is too high. > > Are you thinking we'll cut over the SVN instantaneously, or maintain > > parallel CVS and SVN lines for a while? > > That's a good question. Basically, it boils down to "what's happening > between 2.4.0 and 3.0.0?" Ie. should we put bug fixes in CVS in > anticipation of a 2.4.1? We'll have to keep the 2.4 line alive for a while, probably in kde's cvs, so we can put critical bug fixes on it. I'm not in favour of doing any real development on the 2.4 line once it's out (else why call it a stable branch ?) I also think that 2.4's lure will diminish rapidly as the 3.0 line comes together. Although the merging is likely to be bumpy, once that's done I don't foresee major delays in getting usably stable builds from that line. Vex's x86 support is already pretty much as solid as the old UCode line, and in some ways better. What's between 2.4 and 3.0 ? What I want to do is: * Rewrite the low level memory manager, for the reasons already discussed at length. * Restructure the coregrind/ swamp into separate, well-defined subsystems. * Make amd64 work as well as x86. * Put primary emphasis on better structure, clarity and maintainability of the system as a whole. I've noticed that neglect of these things over the long term is a leading cause of death/abandonment of software systems, and I don't want Valgrind to fall into that trap. My goal for 3.0 is to support x86-linux, amd64-linux and possibly ppc32-linux. I'm not interested in merging support for alternative OSs until after that point, although I do of course hope that folks like GregP can start to construct changesets based on the 3.0 branch for supporting other OSs. Once past 3.0, we can figure out how to fold those in. I would like to have the source base shaping up for a 3.0 release by June 05. > > How about bugs? Are we going to continue using kde > > bugzilla, or start a new bug system? kde.org's CVS/bugzilla integration > > is rather nice; would we be able to reproduce that? Let's stick with kde's bugzilla for a while, and with SF's lists. There's already a lot changing at once here, and those work well for us. J |
|
From: Nicholas N. <nj...@cs...> - 2005-03-05 13:23:06
|
On Fri, 4 Mar 2005, Jeremy Fitzhardinge wrote: >> I'm still using the --in-place method. > > Er, I don't think so; that hasn't been implemented in a very long time... > : abulafia:pts/6; grep -- --in-place */*.[ch] > exit status 1 Oh yeah, my bad. N |
|
From: Jeremy F. <je...@go...> - 2005-03-05 11:08:20
|
CVS commit by fitzhardinge:
Wider match for writev in X suppression
M +1 -1 xfree-4.supp 1.11
--- valgrind/xfree-4.supp #1.10:1.11
@@ -120,5 +120,5 @@
Memcheck:Param
writev(vector[...])
- fun:__writev
+ fun:*_writev
fun:_X11TransSocketWritev
fun:_X11TransWritev
|
|
From: Jeremy F. <je...@go...> - 2005-03-05 07:44:40
|
CVS commit by fitzhardinge: Fix VALGRINDLIB instructions. M +1 -1 README_DEVELOPERS 1.6 --- valgrind/README_DEVELOPERS #1.5:1.6 @@ -7,5 +7,5 @@ of the source tree (and must be an absolute path). Eg: - VALGRINDLIB=~/grind/head4 ~/grind/head4/coregrind/valgrind + VALGRINDLIB=~/grind/head4/.in_place ~/grind/head4/coregrind/valgrind This allows you to compile and run with "make" instead of "make install", |
|
From: Jeremy F. <je...@go...> - 2005-03-05 07:42:53
|
CVS commit by fitzhardinge:
Make libpthread strstr suppression a bit more general.
M +4 -4 glibc-2.3.supp 1.24
--- valgrind/glibc-2.3.supp #1.23:1.24
@@ -252,6 +252,6 @@
fun:strstr
fun:__pthread_initialize_minimal
- obj:/lib/tls/libpthread-0.61.so
- obj:/lib/tls/libpthread-0.61.so
+ obj:/lib/tls/libpthread*.so*
+ obj:/lib/tls/libpthread*.so*
}
{
@@ -260,6 +260,6 @@
fun:strstr
fun:pthread_initialize
- obj:/lib/i686/libpthread-0.10.so
- obj:/lib/i686/libpthread-0.10.so
+ obj:/lib/i686/libpthread*.so*
+ obj:/lib/i686/libpthread*.so*
}
{
|
|
From: Jeremy F. <je...@go...> - 2005-03-05 07:22:48
|
CVS commit by fitzhardinge:
Update suppressions for X on FC3
M +48 -1 xfree-4.supp 1.10
--- valgrind/xfree-4.supp #1.9:1.10
@@ -120,8 +120,8 @@
Memcheck:Param
writev(vector[...])
- fun:vgAllRoadsLeadToRome_writev
fun:__writev
fun:_X11TransSocketWritev
fun:_X11TransWritev
+ fun:*
}
@@ -136,4 +136,51 @@
}
+{
+ Xorg 6.8.1 uninit _write* padding
+ Memcheck:Param
+ write(buf)
+ fun:__write*
+ fun:_X11TransWrite
+ obj:/usr/X11R6/lib/libX11.so.6.2
+}
+
+{
+ Xorg 6.8.1 uninit write padding
+ Memcheck:Param
+ write(buf)
+ fun:write
+ fun:_X11TransWrite
+ obj:/usr/X11R6/lib/libX11.so.6.2
+}
+
+{
+ Xorg 6.8.1 ICE uninit __write* padding
+ Memcheck:Param
+ write(buf)
+ fun:__write*
+ fun:_IceTransWrite
+ fun:_IceWrite
+ fun:IceFlush
+}
+
+{
+ Xorg 6.8.1 ICE uninit write padding
+ Memcheck:Param
+ write(buf)
+ fun:write
+ fun:_IceTransWrite
+ fun:_IceWrite
+ fun:IceFlush
+}
+
+{
+ Xorg 6.8.1 writev uninit padding
+ Memcheck:Param
+ writev(vector[...])
+ fun:writev
+ obj:/usr/X11R6/lib/libX11.so.6.2
+ fun:_X11TransWritev
+ fun:_XSend
+}
##----------------------------------------------------------------------##
|
|
From: <js...@ac...> - 2005-03-05 04:04:21
|
Nightly build on phoenix ( SuSE 9.1 ) started at 2005-03-05 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_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int rm: cannot remove `vgcore.pid*': No such file or directory (cleanup operation failed: rm vgcore.pid*) 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 ---------------------------------------- == 198 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: Tom H. <to...@co...> - 2005-03-05 03:28:15
|
Nightly build on dunsmere ( Fedora Core 3 ) started at 2005-03-05 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_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: 10048 Segmentation fault VALGRINDLIB=/tmp/valgrind.17469/valgrind/.in_place /tmp/valgrind.17469/valgrind/./coregrind/valgrind --command-line-only=yes --tool=none ./int >int.stdout.out 2>int.stderr.out rm: cannot remove `vgcore.pid*': No such file or directory (cleanup operation failed: rm vgcore.pid*) 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 ---------------------------------------- == 204 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-05 03:22:09
|
Nightly build on audi ( Red Hat 9 ) started at 2005-03-05 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 rm: cannot remove `vgcore.pid*': No such file or directory (cleanup operation failed: rm vgcore.pid*) 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 ---------------------------------------- == 203 tests, 0 stderr failures, 0 stdout failures ================= |
|
From: Tom H. <th...@cy...> - 2005-03-05 03:16:20
|
Nightly build on ginetta ( Red Hat 8.0 ) started at 2005-03-05 03:10:02 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow 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 rm: cannot remove `vgcore.pid*': No such file or directory (cleanup operation failed: rm vgcore.pid*) 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 ---------------------------------------- == 202 tests, 2 stderr failures, 0 stdout failures ================= memcheck/tests/pth_once (stderr) memcheck/tests/threadederrno (stderr) make: *** [regtest] Error 1 |
|
From: Tom H. <th...@cy...> - 2005-03-05 03:15:25
|
Nightly build on standard ( Red Hat 7.2 ) started at 2005-03-05 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_sse: valgrind ./insn_sse insn_sse2: (skipping, prereq failed: ../../../tests/cputest x86-sse2) int: valgrind ./int rm: cannot remove `vgcore.pid*': No such file or directory (cleanup operation failed: rm vgcore.pid*) 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 ---------------------------------------- == 202 tests, 5 stderr failures, 0 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pth_once (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-05 03:11:44
|
Nightly build on alvis ( Red Hat 7.3 ) started at 2005-03-05 03:05:02 GMT Checking out source tree ... done Configuring ... done Building ... done Running regression tests ... done Last 20 lines of log.verbose follow == 202 tests, 17 stderr failures, 0 stdout failures ================= memcheck/tests/addressable (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/pth_once (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) massif/tests/toobig-allocs (stderr) massif/tests/true_html (stderr) massif/tests/true_text (stderr) make: *** [regtest] Error 1 |
|
From: Jeremy F. <je...@go...> - 2005-03-05 02:33:02
|
Nicholas Nethercote wrote:
> [~/grind/head6] VALGRINDLIB=~/grind/head6
> ~/grind/head6/coregrind/valgrind
>
> valgrind: failed to load /u/njn/grind/head6/stage2: No such file or
> directory
Yeah, it should be .../head6/.in_place. I'll fix it later, if you don't
get there first.
> I'm still using the --in-place method.
Er, I don't think so; that hasn't been implemented in a very long time...
: abulafia:pts/6; grep -- --in-place */*.[ch]
exit status 1
J
|
|
From: Nicholas N. <nj...@cs...> - 2005-03-05 02:06:49
|
On Sat, 5 Mar 2005, Jeremy Fitzhardinge wrote: > +To run Valgrind without having to install it, run coregrind/valgrind > +with the VALGRINDLIB environment variable set, where <dir> is the root > +of the source tree (and must be an absolute path). Eg: > + > + VALGRINDLIB=~/grind/head4 ~/grind/head4/coregrind/valgrind That doesn't work for me: [~/grind/head6] VALGRINDLIB=~/grind/head6 ~/grind/head6/coregrind/valgrind valgrind: failed to load /u/njn/grind/head6/stage2: No such file or directory I'm still using the --in-place method. N |
|
From: Nicholas N. <nj...@cs...> - 2005-03-05 02:03:51
|
On Fri, 4 Mar 2005, Jeremy Fitzhardinge wrote: > Did we decide on --leak-check=summary or full/yes as the default? Julian said: Ok. I change my vote. Let's have --leak-check=yes|summary|no, with the default being yes, and summary ... well, just producing a summary. When =yes is in effect, we should also print a line saying "use ...=summary or ...=no to reduce the amount of output." > We could either edit all the .vgtest files, or all the stderr.exp > files. Or change vgtest itself to always supply --leak-check=no as an arg. I worry that turning on the leak checker in all the tests will cause lots of failures -- the leak check numbers seem a bit variable. I vote for editing all the .vgtest files. N |
|
From: Jeremy F. <je...@go...> - 2005-03-05 02:02:10
|
CVS commit by fitzhardinge: Update doc install rules and valgrind.spec.in to install docs in $(prefix)/share/doc/valgrind-$(VERSION), which seems to be consistent with what everyone else does. Also update the spec's epoch, so that it will compare as newer than the FC3 valgrind package. M +3 -2 Makefile.all.am 1.2 M +2 -1 valgrind.spec.in 1.21 M +1 -1 addrcheck/docs/Makefile.am 1.4 M +1 -1 cachegrind/docs/Makefile.am 1.4 M +1 -1 corecheck/docs/Makefile.am 1.4 M +1 -1 coregrind/docs/Makefile.am 1.6 M +1 -1 docs/Makefile.am 1.5 M +1 -1 helgrind/docs/Makefile.am 1.4 M +1 -1 lackey/docs/Makefile.am 1.4 M +1 -1 massif/docs/Makefile.am 1.3 M +1 -1 memcheck/docs/Makefile.am 1.4 M +1 -1 none/docs/Makefile.am 1.4 --- valgrind/valgrind.spec.in #1.20:1.21 @@ -3,4 +3,5 @@ Version: @VERSION@ Release: 1 +Epoch: 2 Copyright: GPL Group: Development/Debuggers @@ -52,5 +53,5 @@ %doc -/usr/share/doc/valgrind/* +/usr/share/doc/valgrind-@VERSION@/* %clean --- valgrind/Makefile.all.am #1.1:1.2 @@ -1,8 +1,9 @@ -## This file should be included by *every* Makefile.am, except those for docs/ -## and tests/ subdirectories. +## This file should be included by *every* Makefile.am, except those for +## tests/ subdirectories. valdir = $(libdir)/valgrind inplacedir = $(top_builddir)/.in_place +docdir = $(datadir)/doc/valgrind-$(VERSION) --- valgrind/docs/Makefile.am #1.4:1.5 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = manual.html --- valgrind/lackey/docs/Makefile.am #1.3:1.4 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = lk_main.html --- valgrind/cachegrind/docs/Makefile.am #1.3:1.4 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = cg_main.html cg_techdocs.html --- valgrind/none/docs/Makefile.am #1.3:1.4 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = nl_main.html --- valgrind/massif/docs/Makefile.am #1.2:1.3 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = ms_main.html date.gif --- valgrind/addrcheck/docs/Makefile.am #1.3:1.4 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = ac_main.html --- valgrind/corecheck/docs/Makefile.am #1.3:1.4 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = cc_main.html --- valgrind/memcheck/docs/Makefile.am #1.3:1.4 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = mc_main.html mc_techdocs.html --- valgrind/helgrind/docs/Makefile.am #1.3:1.4 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = hg_main.html --- valgrind/coregrind/docs/Makefile.am #1.5:1.6 @@ -1,3 +1,3 @@ -docdir = $(datadir)/doc/valgrind +include $(top_srcdir)/Makefile.all.am dist_doc_DATA = coregrind_core.html coregrind_intro.html coregrind_tools.html |
|
From: Jeremy F. <je...@go...> - 2005-03-05 01:58:53
|
CVS commit by fitzhardinge: Fix up old stuff in README_DEVELOPERS M +5 -8 README_DEVELOPERS 1.5 --- valgrind/README_DEVELOPERS #1.4:1.5 @@ -2,9 +2,10 @@ Building and not installing it ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -To run Valgrind without having to install it, run coregrind/valgrind (prefix -with "sh" because it's not executable) with the --in-place=<dir> option, where -<dir> is the root of the source tree (and must be an absolute path). Eg: - sh ~/grind/head4/coregrind/valgrind --in-place=/homes/njn25/grind/head4 +To run Valgrind without having to install it, run coregrind/valgrind +with the VALGRINDLIB environment variable set, where <dir> is the root +of the source tree (and must be an absolute path). Eg: + + VALGRINDLIB=~/grind/head4 ~/grind/head4/coregrind/valgrind This allows you to compile and run with "make" instead of "make install", @@ -50,6 +51,2 @@ jump *$eip -Code that runs in the target program such as the pthread replacement -code or the malloc replacement code would have to be debugged as part -of the target program, probably by attaching a debugger after it has -started. We are not sure if this would work, however. |