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
(9) |
2
(11) |
3
(3) |
4
(7) |
5
(15) |
|
6
(10) |
7
(9) |
8
(12) |
9
(10) |
10
(6) |
11
(12) |
12
(12) |
|
13
(11) |
14
(14) |
15
(18) |
16
(15) |
17
(19) |
18
(15) |
19
(9) |
|
20
|
21
(5) |
22
(10) |
23
(15) |
24
(18) |
25
(20) |
26
(15) |
|
27
(14) |
28
(11) |
29
(17) |
30
(17) |
31
(23) |
|
|
|
From: Philippe W. <phi...@sk...> - 2014-07-25 22:24:41
|
On Fri, 2014-07-25 at 13:34 +0200, Florian Krohm wrote:
> I have been looking at get_sym_name and its various wrapper
> functions (such as get_fnname_w_offset). Those functions all take
> a character buffer as argument for the symbol name they
> are supposed to obtain and return a boolean result indicating
> success or not. On failure, the symbol name is not written to
> (debuginfo.c, line 1640).
>
> That was a surprise to me in the sense that I would have expected
> a return argument to always be initialised as that is semantically
> easier and less fragile.
>
> We are also missing an opportunity here to have the name of the
> unknown symbol be unique and hard-wired in a single place
> (in get_sym_name).
>
> Currently there are at least three names for the unknown symbol
> and I don't think they are that way by design :)
>
> (a) m_sbprofile.c, line 87: name = ""
> (b) m_translate.c, line 1418: name = "UNKNOWN_FUNCTION"
> (c) m_translate.c, line 1393: name = "???"
>
> I'm proposing to change get_sym_name to initialise its return buffer
> with the name of the unknown symbol (patch below) and adjust all
> call sites accordingly. We can then get rid of the various
> sprinkles of
>
> ok = VG_(get_fnname_w_offset)(addr, name2, sizeof(name2));
> if (!ok) VG_(strcpy)(name2, "???");
>
> that we have in several places.
>
> Any objections?
Looks a good idea to me.
Some feedback:
* need to avoid a similar perf regression as brought in by rev 14186
we might have to rewrite (and maybe rename) VG_(strncpy_safely)
to make it less strncpy like.
* Maybe some messages might become less understandable if replacing
"UNKNOWN_FUNCTION" by "???"
e.g.
VG_(printf("I got a problem in %s\n", fn);
might change of output from
I got a problem in UNKNOWN_FUNCTION
to
I got a problem in ???
So it might be needed to examine the callers and see what they do
with the result.
Philippe
|
|
From: Philippe W. <phi...@sk...> - 2014-07-25 22:15:20
|
On Fri, 2014-07-25 at 05:58 -0700, John Reiser wrote: > > + VG_(strncpy_safely)(buf, "???", nbuf); // unknown symbol > > Beware performance loss. strncpy _always_ writes nbuf bytes (3rd argument), > so the execution of that code finishes with the equivalent of > memset(&buf[3], 0, nbuf - 3); > > This will be much faster: > memcpy(buf, "???", 3+1); > as long as the other code requires only one terminating '\0'. > [Dress up with the appropriate VG_() and other adornments.] Funny that we just got a big performance regression due to the rewriting of VG_(strncpy_safely) : it was not zero-filling and since rev 14186, it is zero filling. That gave for some tests more than 50% perf regressions. Philippe |
|
From: <sv...@va...> - 2014-07-25 20:46:14
|
Author: philippe
Date: Fri Jul 25 20:46:01 2014
New Revision: 14192
Log:
Have m_addrinfo.c giving more details about an address in a text segment
(using a fake 'one address' stack trace).
This a.o. can be used with the gdbsrv 'monitor v.info location 0x.....'
to compare gdb and valgrind address to source mapping.
Any tool that use pub_tool_addrinfo.h will also better descrive
text addresses.
No impact on tests, as there is no test testing 'segment' address
description :(
Modified:
trunk/coregrind/m_addrinfo.c
Modified: trunk/coregrind/m_addrinfo.c
==============================================================================
--- trunk/coregrind/m_addrinfo.c (original)
+++ trunk/coregrind/m_addrinfo.c Fri Jul 25 20:46:01 2014
@@ -433,6 +433,11 @@
VG_(pp_SectKind)(ai->Addr.SectKind.kind),
ai->Addr.SectKind.objname,
xpost );
+ if (ai->Addr.SectKind.kind == Vg_SectText) {
+ /* To better describe the address in a text segment,
+ pp a dummy stacktrace made of this single address. */
+ VG_(pp_StackTrace)( &a, 1 );
+ }
break;
default:
|
|
From: Philippe W. <phi...@sk...> - 2014-07-25 19:37:10
|
On Fri, 2014-07-25 at 08:07 +0200, Philippe Waroquiers wrote:
> Intuitively, the biggest change (the VexendNess change) is
> the first candidate to look at.
And as extremely often with performance related subjects,
intuition gives reliable guesses, as reliable as
interpreting the way the birds fly
or as a crystal ball,
or interpret coffee grounds
and other similar scientific ways to predict perf impact.
So, it is not at all the VexendNess change.
Rather from (manual) bisect, the regression is caused by r14186,
which is given below.
The perf problem is created because the new
implementation of VG_(strncpy_safely) "paints" complete big
arrays of chars with null bytes.
strncpy man page:
If the length of src is less than n, strncpy() pads the remainder of
dest with null bytes.
So, VG_(strncpy_safely) was not compliant with strncpy manual,
and is now compliant on that padding aspect, but causes a huge
performance regression (and explicitely differs in behaviour from
strncpy/VG_(strncpy)).
svn diff -r 14185:14186
Index: coregrind/m_debuginfo/debuginfo.c
===================================================================
--- coregrind/m_debuginfo/debuginfo.c (revision 14185)
+++ coregrind/m_debuginfo/debuginfo.c (revision 14186)
@@ -1870,7 +1870,6 @@
&& di->text_avma <= a
&& a < di->text_avma + di->text_size) {
VG_(strncpy_safely)(buf, di->fsm.filename, nbuf);
- buf[nbuf-1] = 0;
return True;
}
}
Index: coregrind/m_libcbase.c
===================================================================
--- coregrind/m_libcbase.c (revision 14185)
+++ coregrind/m_libcbase.c (revision 14186)
@@ -304,14 +304,8 @@
{
libcbase_assert(ndest > 0);
- SizeT i = 0;
- while (True) {
- dest[i] = 0;
- if (src[i] == 0) return;
- if (i >= ndest-1) return;
- dest[i] = src[i];
- i++;
- }
+ VG_(strncpy)(dest, src, ndest);
+ dest[ndest - 1] = '\0';
}
HChar* VG_(strncpy) ( HChar* dest, const HChar* src, SizeT ndest )
|
|
From: John R.
|
> + VG_(strncpy_safely)(buf, "???", nbuf); // unknown symbol Beware performance loss. strncpy _always_ writes nbuf bytes (3rd argument), so the execution of that code finishes with the equivalent of memset(&buf[3], 0, nbuf - 3); This will be much faster: memcpy(buf, "???", 3+1); as long as the other code requires only one terminating '\0'. [Dress up with the appropriate VG_() and other adornments.] |
|
From: Florian K. <fl...@ei...> - 2014-07-25 11:34:19
|
I have been looking at get_sym_name and its various wrapper
functions (such as get_fnname_w_offset). Those functions all take
a character buffer as argument for the symbol name they
are supposed to obtain and return a boolean result indicating
success or not. On failure, the symbol name is not written to
(debuginfo.c, line 1640).
That was a surprise to me in the sense that I would have expected
a return argument to always be initialised as that is semantically
easier and less fragile.
We are also missing an opportunity here to have the name of the
unknown symbol be unique and hard-wired in a single place
(in get_sym_name).
Currently there are at least three names for the unknown symbol
and I don't think they are that way by design :)
(a) m_sbprofile.c, line 87: name = ""
(b) m_translate.c, line 1418: name = "UNKNOWN_FUNCTION"
(c) m_translate.c, line 1393: name = "???"
I'm proposing to change get_sym_name to initialise its return buffer
with the name of the unknown symbol (patch below) and adjust all
call sites accordingly. We can then get rid of the various
sprinkles of
ok = VG_(get_fnname_w_offset)(addr, name2, sizeof(name2));
if (!ok) VG_(strcpy)(name2, "???");
that we have in several places.
Any objections?
Florian
Index: coregrind/m_debuginfo/debuginfo.c
===================================================================
--- coregrind/m_debuginfo/debuginfo.c (revision 14190)
+++ coregrind/m_debuginfo/debuginfo.c (working copy)
@@ -1636,8 +1636,10 @@
PtrdiffT offset;
search_all_symtabs ( a, &di, &sno, match_anywhere_in_sym, findText );
- if (di == NULL)
+ if (di == NULL) {
+ VG_(strncpy_safely)(buf, "???", nbuf); // unknown symbol
return False;
+ }
vg_assert(di->symtab[sno].pri_name);
VG_(demangle) ( do_cxx_demangling, do_z_demangling,
|
|
From: <sv...@va...> - 2014-07-25 08:38:11
|
Author: florian
Date: Fri Jul 25 08:38:02 2014
New Revision: 14191
Log:
Add LIKELY as suggested by Philippe.
Modified:
trunk/coregrind/m_aspacemgr/priv_aspacemgr.h
trunk/coregrind/m_libcbase.c
Modified: trunk/coregrind/m_aspacemgr/priv_aspacemgr.h
==============================================================================
--- trunk/coregrind/m_aspacemgr/priv_aspacemgr.h (original)
+++ trunk/coregrind/m_aspacemgr/priv_aspacemgr.h Fri Jul 25 08:38:02 2014
@@ -77,7 +77,7 @@
const HChar* fn );
#define aspacem_assert(expr) \
- ((void) ((expr) ? 0 : \
+ ((void) (LIKELY(expr) ? 0 : \
(ML_(am_assert_fail)(#expr, \
__FILE__, __LINE__, \
__PRETTY_FUNCTION__))))
Modified: trunk/coregrind/m_libcbase.c
==============================================================================
--- trunk/coregrind/m_libcbase.c (original)
+++ trunk/coregrind/m_libcbase.c Fri Jul 25 08:38:02 2014
@@ -35,11 +35,11 @@
/* ---------------------------------------------------------------------
- Assert machinery for use in this file. VG_(assert) cannot be called
+ Assert machinery for use in this file. vg_assert cannot be called
here due to cyclic dependencies.
------------------------------------------------------------------ */
#define libcbase_assert(expr) \
- ((void) ((expr) ? 0 : \
+ ((void) (LIKELY(expr) ? 0 : \
(ML_(libcbase_assert_fail)(#expr, \
__FILE__, __LINE__, \
__PRETTY_FUNCTION__))))
|
|
From: Philippe W. <phi...@sk...> - 2014-07-25 06:30:26
|
On Fri, 2014-07-25 at 07:11 +0100, Tom Hughes wrote: > Well I haven't deliberately disabled anything for any of my test > systems, and this is the first I've heard of the idea of a "perf > measurement enabled" build. > > What exactly does this involve? I saw I only replied in terms of configuration, while that of course involves also cpu consumption :). In terms of cpu, if you configure to run for both valgrind-old and valgrind-new (easier to compare), with the rest being defaulted, I guess it costs between 30 minutes to 2 or 3 hours of cpu, depending on the computer (gcc110 is one hour, the suse/s390 uses somewhat more. I guess an ARM system will take 3 hours or so). Modern intel should be faster (30 minutes ? 45 minutes) ? The cpu time spent for perf is given in the nightly mail, after the comparison Philippe |
|
From: Philippe W. <phi...@sk...> - 2014-07-25 06:17:32
|
On Fri, 2014-07-25 at 07:11 +0100, Tom Hughes wrote: > On 25/07/14 07:07, Philippe Waroquiers wrote: > > > NB: we only have a ppc64 and s390 "perf measurement enabled" nightly > > build, which is maybe not good enough (we are lacking many platforms, > > in particular x86 and amd64). > > Any volunteers having computers doing nothing most of the time ? > > :) > > Well I haven't deliberately disabled anything for any of my test > systems, and this is the first I've heard of the idea of a "perf > measurement enabled" build. > > What exactly does this involve? The gcc110 conf file I am using is: export ABT_DETAILS="`head -1 /etc/issue`, `uname -m`" export ABT_JOBS=16 export ABT_PERF="--vg=../valgrind-new --vg=../valgrind-old" There are other vars you can set to configure the perf tests e.g. depending on the cpu you want to allow for such perf, you can run the perf for a subset of the tools, or do less 'repeats', or only valgrind-new or ... See nightly/README.txt for more details. Philippe |
|
From: Tom H. <to...@co...> - 2014-07-25 06:12:10
|
On 25/07/14 07:07, Philippe Waroquiers wrote: > NB: we only have a ppc64 and s390 "perf measurement enabled" nightly > build, which is maybe not good enough (we are lacking many platforms, > in particular x86 and amd64). > Any volunteers having computers doing nothing most of the time ? > :) Well I haven't deliberately disabled anything for any of my test systems, and this is the first I've heard of the idea of a "perf measurement enabled" build. What exactly does this involve? Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Philippe W. <phi...@sk...> - 2014-07-25 06:07:43
|
The 2 nightly builds that have perf comparison enabled (gcc110/fedora20/ppc64, sless390/suse11/s390) have huge difference in performance between valgrind-old and valgrind-new. (the pattern of what slows down is not always the same but both shows big regressions e.g. in massif or memcheck). massif seems consistenly slowed down on s390 and ppc64. We also have other huge slowdown at various places. I re-measured on gcc110/ppc64 the memcheck/heap_pdb4 slowdown. heap_pdb4 on my old pentium seems also to slowdown significantly for massif (40%). So, it looks like a commit between r14183 and 14190 causes this. They are a bunch of changes (we work too hard :) so several candidates are possible. Intuitively, the biggest change (the VexendNess change) is the first candidate to look at. Philippe NB: we only have a ppc64 and s390 "perf measurement enabled" nightly build, which is maybe not good enough (we are lacking many platforms, in particular x86 and amd64). Any volunteers having computers doing nothing most of the time ? :) |
|
From: Christian B. <bor...@de...> - 2014-07-25 04:13:54
|
valgrind revision: 14190 VEX revision: 2910 C compiler: gcc (SUSE Linux) 4.3.4 [gcc-4_3-branch revision 152973] GDB: GNU gdb (GDB) SUSE (7.5.1-0.7.29) Assembler: GNU assembler (GNU Binutils; SUSE Linux Enterprise 11) 2.23.1 C library: GNU C Library stable release version 2.11.3 (20110527) uname -mrs: Linux 3.0.101-0.31-default s390x Vendor version: Welcome to SUSE Linux Enterprise Server 11 SP3 (s390x) - Kernel %r (%t). Nightly build on sless390 ( SUSE Linux Enterprise Server 11 SP3 gcc 4.3.4 on z196 (s390x) ) Started at 2014-07-25 03:45:01 CEST Ended at 2014-07-25 06:13:40 CEST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 657 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/origin5-bz2 (stderr) helgrind/tests/pth_cond_destroy_busy (stderr) helgrind/tests/tc20_verifywrap (stderr) --tools=none,memcheck,callgrind,helgrind,cachegrind,drd,massif --reps=3 --vg=../valgrind-new --vg=../valgrind-old -- Running tests in perf ---------------------------------------------- -- bigcode1 -- bigcode1 valgrind-new:0.23s no: 4.9s (21.3x, -----) me: 6.2s (27.2x, -----) ca:26.6s (115.6x, -----) he: 5.5s (23.9x, -----) ca: 9.2s (40.0x, -----) dr: 4.8s (20.8x, -----) ma: 3.9s (17.1x, -----) bigcode1 valgrind-old:0.23s no: 4.7s (20.6x, 3.5%) me: 6.2s (27.0x, 0.6%) ca:26.4s (115.0x, 0.5%) he: 5.8s (25.1x, -5.1%) ca: 9.1s (39.7x, 0.9%) dr: 4.8s (21.0x, -1.0%) ma: 4.9s (21.4x,-24.9%) -- bigcode2 -- bigcode2 valgrind-new:0.25s no: 7.9s (31.5x, -----) me:13.1s (52.4x, -----) ca:39.4s (157.5x, -----) he:10.5s (42.1x, -----) ca:14.3s (57.3x, -----) dr: 8.9s (35.7x, -----) ma: 7.4s (29.5x, -----) bigcode2 valgrind-old:0.25s no: 7.7s (30.7x, 2.7%) me:13.2s (52.8x, -0.9%) ca:39.7s (158.7x, -0.7%) he:10.8s (43.0x, -2.2%) ca:14.3s (57.1x, 0.3%) dr: 9.0s (36.1x, -1.0%) ma: 8.3s (33.2x,-12.8%) -- bz2 -- bz2 valgrind-new:0.69s no: 6.7s ( 9.7x, -----) me:12.7s (18.4x, -----) ca:31.0s (44.9x, -----) he:19.8s (28.7x, -----) ca:34.6s (50.2x, -----) dr:28.9s (41.9x, -----) ma: 4.2s ( 6.0x, -----) bz2 valgrind-old:0.69s no: 5.9s ( 8.6x, 10.9%) me:12.7s (18.4x, 0.0%) ca:30.7s (44.6x, 0.8%) he:19.6s (28.3x, 1.1%) ca:34.4s (49.8x, 0.8%) dr:28.9s (41.9x, 0.2%) ma: 5.2s ( 7.6x,-25.7%) -- fbench -- fbench valgrind-new:0.41s no: 1.6s ( 4.0x, -----) me: 4.2s (10.4x, -----) ca: 9.4s (23.0x, -----) he: 6.3s (15.4x, -----) ca: 7.3s (17.9x, -----) dr: 5.5s (13.5x, -----) ma: 1.6s ( 4.0x, -----) fbench valgrind-old:0.41s no: 1.6s ( 3.9x, 0.6%) me: 4.2s (10.4x, 0.0%) ca: 9.4s (23.0x, 0.2%) he: 6.4s (15.7x, -1.9%) ca: 7.3s (17.7x, 1.2%) dr: 5.5s (13.5x, 0.0%) ma: 1.6s ( 4.0x, 0.0%) -- ffbench -- ffbench valgrind-new:0.21s no: 1.2s ( 5.6x, -----) me: 3.0s (14.0x, -----) ca: 3.1s (14.9x, -----) he:45.2s (215.1x, -----) ca: 9.7s (46.2x, -----) dr: 6.9s (33.0x, -----) ma: 1.0s ( 4.6x, -----) ffbench valgrind-old:0.21s no: 1.1s ( 5.3x, 5.9%) me: 3.0s (14.1x, -0.3%) ca: 3.0s (14.3x, 3.5%) he:43.0s (204.8x, 4.8%) ca: 9.6s (45.8x, 1.0%) dr: 6.9s (32.8x, 0.4%) ma: 1.0s ( 4.7x, -2.1%) -- heap -- heap valgrind-new:0.23s no: 2.3s (10.1x, -----) me: 8.7s (38.0x, -----) ca:13.2s (57.5x, -----) he:12.9s (56.2x, -----) ca:11.4s (49.8x, -----) dr: 7.6s (33.0x, -----) ma:27.7s (120.3x, -----) heap valgrind-old:0.23s no: 2.2s ( 9.4x, 7.3%) me: 8.8s (38.3x, -0.8%) ca:13.2s (57.3x, 0.4%) he:12.9s (56.0x, 0.3%) ca:11.5s (49.9x, -0.3%) dr: 7.8s (33.8x, -2.4%) ma: 7.9s (34.3x, 71.4%) -- heap_pdb4 -- heap_pdb4 valgrind-new:0.22s no: 2.6s (11.7x, -----) me:12.9s (58.7x, -----) ca:14.3s (65.1x, -----) he:14.2s (64.8x, -----) ca:12.6s (57.1x, -----) dr: 8.5s (38.8x, -----) ma:28.4s (129.1x, -----) heap_pdb4 valgrind-old:0.22s no: 2.4s (10.9x, 7.0%) me:12.9s (58.9x, -0.2%) ca:14.2s (64.7x, 0.6%) he:14.1s (64.1x, 1.0%) ca:12.4s (56.3x, 1.5%) dr: 8.8s (39.8x, -2.5%) ma: 8.1s (36.9x, 71.5%) -- many-loss-records -- many-loss-records valgrind-new:0.03s no: 0.5s (18.0x, -----) me: 2.1s (70.7x, -----) ca: 2.0s (68.0x, -----) he: 2.2s (72.0x, -----) ca: 2.0s (66.7x, -----) dr: 1.7s (55.3x, -----) ma: 5.1s (169.3x, -----) many-loss-records valgrind-old:0.03s no: 0.5s (17.3x, 3.7%) me: 2.1s (70.3x, 0.5%) ca: 1.9s (64.7x, 4.9%) he: 2.1s (71.7x, 0.5%) ca: 1.9s (64.0x, 4.0%) dr: 1.8s (58.7x, -6.0%) ma: 1.6s (54.7x, 67.7%) -- many-xpts -- many-xpts valgrind-new:0.07s no: 0.7s ( 9.7x, -----) me: 3.1s (44.9x, -----) ca:381.4s (5448.7x, -----) he: 6.7s (95.1x, -----) ca: 2.9s (41.4x, -----) dr: 2.4s (34.7x, -----) ma: 5.9s (84.3x, -----) many-xpts valgrind-old:0.07s no: 0.7s ( 9.6x, 1.5%) me: 3.2s (45.4x, -1.3%) ca:377.8s (5396.7x, 1.0%) he: 6.6s (93.7x, 1.5%) ca: 2.8s (40.1x, 3.1%) dr: 2.5s (36.1x, -4.1%) ma: 2.6s (36.7x, 56.4%) -- sarp -- sarp valgrind-new:0.03s no: 0.6s (20.3x, -----) me: 3.5s (115.0x, -----) ca: 3.3s (109.7x, -----) he:17.5s (583.3x, -----) ca: 2.1s (70.3x, -----) dr: 1.3s (44.7x, -----) ma: 0.5s (16.0x, -----) sarp valgrind-old:0.03s no: 0.6s (20.3x, 0.0%) me: 3.5s (115.7x, -0.6%) ca: 3.2s (105.3x, 4.0%) he:17.4s (581.3x, 0.3%) ca: 2.0s (68.0x, 3.3%) dr: 1.3s (44.7x, 0.0%) ma: 0.5s (16.0x, 0.0%) -- tinycc -- tinycc valgrind-new:0.22s no: 3.2s (14.5x, -----) me:14.5s (66.0x, -----) ca:30.3s (137.6x, -----) he:28.1s (127.6x, -----) ca:21.5s (97.8x, -----) dr:20.4s (92.7x, -----) ma: 7.3s (33.1x, -----) tinycc valgrind-old:0.22s no: 3.1s (14.3x, 1.6%) me:14.5s (66.0x, 0.0%) ca:29.9s (136.1x, 1.1%) he:27.8s (126.2x, 1.1%) ca:21.2s (96.6x, 1.3%) dr:20.6s (93.7x, -1.0%) ma: 4.1s (18.5x, 44.0%) -- Finished tests in perf ---------------------------------------------- == 11 programs, 154 timings ================= real 115m25.901s user 114m44.162s sys 0m32.310s |
|
From: Tom H. <to...@co...> - 2014-07-25 03:23:59
|
valgrind revision: 14190 VEX revision: 2910 C compiler: gcc (GCC) 4.3.0 20080428 (Red Hat 4.3.0-8) GDB: Assembler: GNU assembler version 2.18.50.0.6-2 20080403 C library: GNU C Library stable release version 2.8 uname -mrs: Linux 3.15.3-200.fc20.x86_64 x86_64 Vendor version: Fedora release 9 (Sulphur) Nightly build on bristol ( x86_64, Fedora 9 ) Started at 2014-07-25 03:51:21 BST Ended at 2014-07-25 04:23:39 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 660 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/amd64/insn-pcmpistri (stderr) memcheck/tests/err_disable4 (stderr) none/tests/amd64/sse4-64 (stdout) |
|
From: Tom H. <to...@co...> - 2014-07-25 02:48:01
|
valgrind revision: 14190 VEX revision: 2910 C compiler: gcc (GCC) 4.6.3 20120306 (Red Hat 4.6.3-2) GDB: GNU gdb (GDB) Fedora (7.3.1-48.fc15) Assembler: GNU assembler version 2.21.51.0.6-6.fc15 20110118 C library: GNU C Library stable release version 2.14.1 uname -mrs: Linux 3.15.3-200.fc20.x86_64 x86_64 Vendor version: Fedora release 15 (Lovelock) Nightly build on bristol ( x86_64, Fedora 15 ) Started at 2014-07-25 03:12:49 BST Ended at 2014-07-25 03:47:49 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) |
|
From: Tom H. <to...@co...> - 2014-07-25 02:37:48
|
valgrind revision: 14190 VEX revision: 2910 C compiler: gcc (GCC) 4.6.3 20120306 (Red Hat 4.6.3-2) GDB: GNU gdb (GDB) Fedora (7.3.50.20110722-16.fc16) Assembler: GNU assembler version 2.21.53.0.1-6.fc16 20110716 C library: GNU C Library development release version 2.14.90 uname -mrs: Linux 3.15.3-200.fc20.x86_64 x86_64 Vendor version: Fedora release 16 (Verne) Nightly build on bristol ( x86_64, Fedora 16 ) Started at 2014-07-25 03:02:09 BST Ended at 2014-07-25 03:37:35 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) drd/tests/tc19_shadowmem (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short 2014-07-25 03:20:10.916056276 +0100 --- new.short 2014-07-25 03:37:35.387062542 +0100 *************** *** 8,12 **** ! == 692 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) - drd/tests/tc19_shadowmem (stderr) --- 8,11 ---- ! == 692 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) |
|
From: Tom H. <to...@co...> - 2014-07-25 02:28:09
|
valgrind revision: 14190 VEX revision: 2910 C compiler: gcc (GCC) 4.7.2 20120921 (Red Hat 4.7.2-2) GDB: GNU gdb (GDB) Fedora (7.4.50.20120120-54.fc17) Assembler: GNU assembler version 2.22.52.0.1-10.fc17 20120131 C library: GNU C Library stable release version 2.15 uname -mrs: Linux 3.15.3-200.fc20.x86_64 x86_64 Vendor version: Fedora release 17 (Beefy Miracle) Nightly build on bristol ( x86_64, Fedora 17 (Beefy Miracle) ) Started at 2014-07-25 02:51:08 BST Ended at 2014-07-25 03:27:53 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 5 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcinfcallRU (stderr) gdbserver_tests/mcinfcallWSRU (stderr) gdbserver_tests/mcmain_pic (stderr) memcheck/tests/err_disable4 (stderr) exp-sgcheck/tests/preen_invars (stdout) exp-sgcheck/tests/preen_invars (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 6 stderr failures, 2 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcinfcallRU (stderr) gdbserver_tests/mcinfcallWSRU (stderr) gdbserver_tests/mcmain_pic (stderr) memcheck/tests/err_disable4 (stderr) none/tests/fdleak_ipv4 (stdout) none/tests/fdleak_ipv4 (stderr) exp-sgcheck/tests/preen_invars (stdout) exp-sgcheck/tests/preen_invars (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short 2014-07-25 03:09:50.012941963 +0100 --- new.short 2014-07-25 03:27:53.839194793 +0100 *************** *** 8,10 **** ! == 692 tests, 6 stderr failures, 2 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcinfcallRU (stderr) --- 8,10 ---- ! == 692 tests, 5 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/mcinfcallRU (stderr) *************** *** 13,16 **** memcheck/tests/err_disable4 (stderr) - none/tests/fdleak_ipv4 (stdout) - none/tests/fdleak_ipv4 (stderr) exp-sgcheck/tests/preen_invars (stdout) --- 13,14 ---- |
|
From: Rich C. <rc...@wi...> - 2014-07-25 02:22:35
|
valgrind revision: 14190
VEX revision: 2910
C compiler: gcc (SUSE Linux) 4.8.1 20130909 [gcc-4_8-branch revision 202388]
GDB: GNU gdb (GDB; openSUSE Factory) 7.6.50.20130731-cvs
Assembler: GNU assembler (GNU Binutils; openSUSE Factory) 2.23.2
C library: GNU C Library (GNU libc) stable release version 2.18 (git )
uname -mrs: Linux 3.11.4-3-desktop x86_64
Vendor version: Welcome to openSUSE 13.1 "Bottle" Beta 1 - Kernel %r (%t).
Nightly build on rodan ( Linux 3.11.4-3-desktop x86_64 )
Started at 2014-07-24 19:22:01 CDT
Ended at 2014-07-24 21:22:23 CDT
Results unchanged from 24 hours ago
Checking out valgrind source tree ... done
Configuring valgrind ... done
Building valgrind ... done
Running regression tests ... failed
Regression test results follow
== 607 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/err_disable3 (stderr)
memcheck/tests/err_disable4 (stderr)
memcheck/tests/threadname (stderr)
memcheck/tests/threadname_xml (stderr)
exp-sgcheck/tests/hackedbz2 (stderr)
=================================================
./valgrind-new/exp-sgcheck/tests/hackedbz2.stderr.diff-glibc28-amd64
=================================================
--- hackedbz2.stderr.exp-glibc28-amd64 2014-07-24 20:22:59.701861089 -0500
+++ hackedbz2.stderr.out 2014-07-24 21:21:12.244592595 -0500
@@ -1,7 +1,6 @@
Invalid read of size 1
- at 0x........: vex_strlen (hackedbz2.c:1006)
- by 0x........: add_to_myprintf_buf (hackedbz2.c:1284)
+ at 0x........: add_to_myprintf_buf (hackedbz2.c:1006)
by 0x........: vex_printf (hackedbz2.c:1155)
by 0x........: BZ2_compressBlock (hackedbz2.c:4039)
by 0x........: handle_compress (hackedbz2.c:4761)
=================================================
./valgrind-new/memcheck/tests/err_disable3.stderr.diff
=================================================
--- err_disable3.stderr.exp 2014-07-24 20:23:02.132887679 -0500
+++ err_disable3.stderr.out 2014-07-24 20:41:54.671258115 -0500
@@ -10,8 +10,6 @@
Thread 2:
Invalid read of size 1
at 0x........: err (err_disable3.c:25)
- by 0x........: child_fn (err_disable3.c:31)
- ...
Address 0x........ is 5 bytes inside a block of size 10 free'd
at 0x........: free (vg_replace_malloc.c:...)
by 0x........: main (err_disable3.c:42)
=================================================
./valgrind-new/memcheck/tests/err_disable4.stderr.diff
=================================================
--- err_disable4.stderr.exp 2014-07-24 20:23:02.976896911 -0500
+++ err_disable4.stderr.out 2014-07-24 20:41:59.099305268 -0500
@@ -1501,8 +1501,6 @@
Thread x:
Invalid read of size 1
at 0x........: err (err_disable4.c:41)
- by 0x........: child_fn_2 (err_disable4.c:55)
- ...
Address 0x........ is 5 bytes inside a block of size 10 free'd
at 0x........: free (vg_replace_malloc.c:...)
by 0x........: main (err_disable4.c:68)
=================================================
./valgrind-new/memcheck/tests/threadname.stderr.diff
=================================================
--- threadname.stderr.exp 2014-07-24 20:23:02.500891705 -0500
+++ threadname.stderr.out 2014-07-24 20:48:11.066270073 -0500
@@ -9,36 +9,12 @@
Thread 2:
Invalid write of size 1
at 0x........: bad_things (threadname.c:16)
- by 0x........: child_fn_0 (threadname.c:53)
- ...
Address 0x........ is 0 bytes after a block of size 2 alloc'd
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: bad_things (threadname.c:15)
by 0x........: child_fn_0 (threadname.c:53)
...
-Thread 3 try1:
-Invalid write of size 1
- at 0x........: bad_things (threadname.c:16)
- by 0x........: child_fn_1 (threadname.c:38)
- ...
- Address 0x........ is 0 bytes after a block of size 3 alloc'd
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: bad_things (threadname.c:15)
- by 0x........: child_fn_1 (threadname.c:38)
- ...
-
-Thread 4 012345678901234:
-Invalid write of size 1
- at 0x........: bad_things (threadname.c:16)
- by 0x........: child_fn_2 (threadname.c:26)
- ...
- Address 0x........ is 0 bytes after a block of size 4 alloc'd
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: bad_things (threadname.c:15)
- by 0x........: child_fn_2 (threadname.c:26)
- ...
-
Thread 1:
Invalid write of size 1
at 0x........: bad_things (threadname.c:16)
=================================================
./valgrind-new/memcheck/tests/threadname_xml.stderr.diff
=================================================
--- threadname_xml.stderr.exp 2014-07-24 20:23:02.836895380 -0500
+++ threadname_xml.stderr.out 2014-07-24 20:48:13.150292307 -0500
@@ -94,14 +94,6 @@
<file>threadname.c</file>
<line>...</line>
</frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_0</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
</stack>
<auxwhat>Address 0x........ is 0 bytes after a block of size 2 alloc'd</auxwhat>
<stack>
@@ -135,112 +127,6 @@
<error>
<unique>0x........</unique>
<tid>...</tid>
- <threadname>try1</threadname>
- <kind>InvalidWrite</kind>
- <what>Invalid write of size 1</what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>bad_things</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_1</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- </stack>
- <auxwhat>Address 0x........ is 0 bytes after a block of size 3 alloc'd</auxwhat>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>malloc</fn>
- <dir>...</dir>
- <file>vg_replace_malloc.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>bad_things</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_1</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- </stack>
-</error>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <threadname>012345678901234</threadname>
- <kind>InvalidWrite</kind>
- <what>Invalid write of size 1</what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>bad_things</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_2</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- </stack>
- <auxwhat>Address 0x........ is 0 bytes after a block of size 4 alloc'd</auxwhat>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<truncated beyond 100 lines>
=================================================
./valgrind-old/exp-sgcheck/tests/hackedbz2.stderr.diff-glibc28-amd64
=================================================
--- hackedbz2.stderr.exp-glibc28-amd64 2014-07-24 19:22:36.232828233 -0500
+++ hackedbz2.stderr.out 2014-07-24 20:21:28.025858431 -0500
@@ -1,7 +1,6 @@
Invalid read of size 1
- at 0x........: vex_strlen (hackedbz2.c:1006)
- by 0x........: add_to_myprintf_buf (hackedbz2.c:1284)
+ at 0x........: add_to_myprintf_buf (hackedbz2.c:1006)
by 0x........: vex_printf (hackedbz2.c:1155)
by 0x........: BZ2_compressBlock (hackedbz2.c:4039)
by 0x........: handle_compress (hackedbz2.c:4761)
=================================================
./valgrind-old/memcheck/tests/err_disable3.stderr.diff
=================================================
--- err_disable3.stderr.exp 2014-07-24 19:22:50.407985845 -0500
+++ err_disable3.stderr.out 2014-07-24 19:42:08.387871226 -0500
@@ -10,8 +10,6 @@
Thread 2:
Invalid read of size 1
at 0x........: err (err_disable3.c:25)
- by 0x........: child_fn (err_disable3.c:31)
- ...
Address 0x........ is 5 bytes inside a block of size 10 free'd
at 0x........: free (vg_replace_malloc.c:...)
by 0x........: main (err_disable3.c:42)
=================================================
./valgrind-old/memcheck/tests/err_disable4.stderr.diff
=================================================
--- err_disable4.stderr.exp 2014-07-24 19:22:51.457997519 -0500
+++ err_disable4.stderr.out 2014-07-24 19:42:12.889921355 -0500
@@ -1501,8 +1501,6 @@
Thread x:
Invalid read of size 1
at 0x........: err (err_disable4.c:41)
- by 0x........: child_fn_2 (err_disable4.c:55)
- ...
Address 0x........ is 5 bytes inside a block of size 10 free'd
at 0x........: free (vg_replace_malloc.c:...)
by 0x........: main (err_disable4.c:68)
=================================================
./valgrind-old/memcheck/tests/threadname.stderr.diff
=================================================
--- threadname.stderr.exp 2014-07-24 19:22:50.411985889 -0500
+++ threadname.stderr.out 2014-07-24 19:48:25.627069426 -0500
@@ -9,36 +9,12 @@
Thread 2:
Invalid write of size 1
at 0x........: bad_things (threadname.c:16)
- by 0x........: child_fn_0 (threadname.c:53)
- ...
Address 0x........ is 0 bytes after a block of size 2 alloc'd
at 0x........: malloc (vg_replace_malloc.c:...)
by 0x........: bad_things (threadname.c:15)
by 0x........: child_fn_0 (threadname.c:53)
...
-Thread 3 try1:
-Invalid write of size 1
- at 0x........: bad_things (threadname.c:16)
- by 0x........: child_fn_1 (threadname.c:38)
- ...
- Address 0x........ is 0 bytes after a block of size 3 alloc'd
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: bad_things (threadname.c:15)
- by 0x........: child_fn_1 (threadname.c:38)
- ...
-
-Thread 4 012345678901234:
-Invalid write of size 1
- at 0x........: bad_things (threadname.c:16)
- by 0x........: child_fn_2 (threadname.c:26)
- ...
- Address 0x........ is 0 bytes after a block of size 4 alloc'd
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: bad_things (threadname.c:15)
- by 0x........: child_fn_2 (threadname.c:26)
- ...
-
Thread 1:
Invalid write of size 1
at 0x........: bad_things (threadname.c:16)
=================================================
./valgrind-old/memcheck/tests/threadname_xml.stderr.diff
=================================================
--- threadname_xml.stderr.exp 2014-07-24 19:22:52.049004090 -0500
+++ threadname_xml.stderr.out 2014-07-24 19:48:27.709092585 -0500
@@ -94,14 +94,6 @@
<file>threadname.c</file>
<line>...</line>
</frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_0</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
</stack>
<auxwhat>Address 0x........ is 0 bytes after a block of size 2 alloc'd</auxwhat>
<stack>
@@ -135,112 +127,6 @@
<error>
<unique>0x........</unique>
<tid>...</tid>
- <threadname>try1</threadname>
- <kind>InvalidWrite</kind>
- <what>Invalid write of size 1</what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>bad_things</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_1</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- </stack>
- <auxwhat>Address 0x........ is 0 bytes after a block of size 3 alloc'd</auxwhat>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>malloc</fn>
- <dir>...</dir>
- <file>vg_replace_malloc.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>bad_things</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_1</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- </stack>
-</error>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <threadname>012345678901234</threadname>
- <kind>InvalidWrite</kind>
- <what>Invalid write of size 1</what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>bad_things</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>child_fn_2</fn>
- <dir>...</dir>
- <file>threadname.c</file>
- <line>...</line>
- </frame>
- </stack>
- <auxwhat>Address 0x........ is 0 bytes after a block of size 4 alloc'd</auxwhat>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
<truncated beyond 100 lines>
|
|
From: Tom H. <to...@co...> - 2014-07-25 02:18:31
|
valgrind revision: 14190 VEX revision: 2910 C compiler: gcc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8) GDB: GNU gdb (GDB) Fedora 7.5.1-42.fc18 Assembler: GNU assembler version 2.23.51.0.1-10.fc18 20120806 C library: GNU C Library stable release version 2.16 uname -mrs: Linux 3.15.3-200.fc20.x86_64 x86_64 Vendor version: Fedora release 18 (Spherical Cow) Nightly build on bristol ( x86_64, Fedora 18 (Spherical Cow) ) Started at 2014-07-25 02:41:11 BST Ended at 2014-07-25 03:18:17 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) exp-sgcheck/tests/preen_invars (stdout) exp-sgcheck/tests/preen_invars (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 3 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) drd/tests/std_atomic (stderr) exp-sgcheck/tests/preen_invars (stdout) exp-sgcheck/tests/preen_invars (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short 2014-07-25 02:59:32.174768899 +0100 --- new.short 2014-07-25 03:18:17.319230797 +0100 *************** *** 8,12 **** ! == 692 tests, 3 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) - drd/tests/std_atomic (stderr) exp-sgcheck/tests/preen_invars (stdout) --- 8,11 ---- ! == 692 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) exp-sgcheck/tests/preen_invars (stdout) |
|
From: Tom H. <to...@co...> - 2014-07-25 02:10:10
|
valgrind revision: 14190 VEX revision: 2910 C compiler: gcc (GCC) 4.8.3 20140624 (Red Hat 4.8.3-1) GDB: GNU gdb (GDB) Fedora 7.6.1-46.fc19 Assembler: GNU assembler version 2.23.52.0.1-9.fc19 20130226 C library: GNU C Library (GNU libc) stable release version 2.17 uname -mrs: Linux 3.15.3-200.fc20.x86_64 x86_64 Vendor version: Fedora release 19 (Schrödingerâs Cat) Nightly build on bristol ( x86_64, Fedora 19 (Schrödingerâs Cat) ) Started at 2014-07-25 02:31:33 BST Ended at 2014-07-25 03:09:55 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) none/tests/fdleak_ipv4 (stderr) exp-sgcheck/tests/hackedbz2 (stderr) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 692 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) exp-sgcheck/tests/hackedbz2 (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short 2014-07-25 02:50:39.497965638 +0100 --- new.short 2014-07-25 03:09:55.710832891 +0100 *************** *** 8,11 **** ! == 692 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) exp-sgcheck/tests/hackedbz2 (stderr) --- 8,12 ---- ! == 692 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) + none/tests/fdleak_ipv4 (stderr) exp-sgcheck/tests/hackedbz2 (stderr) |