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
(5) |
2
(11) |
3
|
4
(9) |
5
(10) |
6
(4) |
7
(14) |
|
8
(15) |
9
(15) |
10
(14) |
11
(13) |
12
(16) |
13
(12) |
14
(9) |
|
15
(21) |
16
(13) |
17
(11) |
18
(13) |
19
(5) |
20
(29) |
21
(20) |
|
22
(13) |
23
(18) |
24
(21) |
25
(17) |
26
(26) |
27
(13) |
28
(17) |
|
29
(10) |
30
(5) |
|
|
|
|
|
|
From: <sv...@va...> - 2014-06-17 20:37:19
|
Author: sewardj
Date: Tue Jun 17 20:37:08 2014
New Revision: 14051
Log:
When printing "REDIR:" lines at -v, print not only the name of the
function being redirected but also the soname of the object that it is
in. This makes it a bit easier to diagnose redirection problems.
Modified:
trunk/coregrind/m_translate.c
Modified: trunk/coregrind/m_translate.c
==============================================================================
--- trunk/coregrind/m_translate.c (original)
+++ trunk/coregrind/m_translate.c Tue Jun 17 20:37:08 2014
@@ -1389,13 +1389,23 @@
HChar name1[512] = "";
HChar name2[512] = "";
name1[0] = name2[0] = 0;
- ok = VG_(get_fnname_w_offset)(nraddr, name1, 512);
+ ok = VG_(get_fnname_w_offset)(nraddr, name1, sizeof(name1));
if (!ok) VG_(strcpy)(name1, "???");
- ok = VG_(get_fnname_w_offset)(addr, name2, 512);
+ ok = VG_(get_fnname_w_offset)(addr, name2, sizeof(name2));
if (!ok) VG_(strcpy)(name2, "???");
+ /* Try also to get the soname (not the filename) of the "from"
+ object. This makes it much easier to debug redirection
+ problems. */
+ const HChar* nraddr_soname = "???";
+ DebugInfo* nraddr_di = VG_(find_DebugInfo)(nraddr);
+ if (nraddr_di) {
+ const HChar* t = VG_(DebugInfo_get_soname)(nraddr_di);
+ if (t)
+ nraddr_soname = t;
+ }
VG_(message)(Vg_DebugMsg,
- "REDIR: 0x%llx (%s) redirected to 0x%llx (%s)\n",
- nraddr, name1,
+ "REDIR: 0x%llx (%s:%s) redirected to 0x%llx (%s)\n",
+ nraddr, nraddr_soname, name1,
addr, name2 );
}
|
|
From: <sv...@va...> - 2014-06-17 20:21:36
|
Author: philippe
Date: Tue Jun 17 20:21:26 2014
New Revision: 14050
Log:
restructure dwarf3 DIE tracing
* add a trace_DIE function
* use it to trace a bad DIE
and to trace all DIEs that are (maybe) read
(due to the "avoid read twice" optimisation, the tracing was not
so easy to read anymore => add an explicit trace_DIE call at the beginning
of read_DIE)
Modified:
trunk/coregrind/m_debuginfo/readdwarf3.c
Modified: trunk/coregrind/m_debuginfo/readdwarf3.c
==============================================================================
--- trunk/coregrind/m_debuginfo/readdwarf3.c (original)
+++ trunk/coregrind/m_debuginfo/readdwarf3.c Tue Jun 17 20:21:26 2014
@@ -1674,31 +1674,30 @@
}
}
-__attribute__((noreturn))
-static void dump_bad_die_and_barf(
- const HChar *whichparser,
+static void trace_DIE(
DW_TAG dtag,
UWord posn,
Int level,
- Cursor* c_die, UWord saved_die_c_offset,
+ UWord saved_die_c_offset,
g_abbv *abbv,
CUConst* cc)
{
+ Cursor c;
FormContents cts;
UInt nf_i;
Bool debug_types_flag;
Bool alt_flag;
- set_position_of_Cursor( c_die, saved_die_c_offset );
posn = uncook_die( cc, posn, &debug_types_flag, &alt_flag );
- VG_(printf)(" <%d><%lx>: %s", level, posn, ML_(pp_DW_TAG)( dtag ) );
- if (debug_types_flag) {
- VG_(printf)(" (in .debug_types)");
- }
- else if (alt_flag) {
- VG_(printf)(" (in alternate .debug_info)");
- }
- VG_(printf)("\n");
+ init_Cursor (&c,
+ debug_types_flag ? cc->escn_debug_types :
+ alt_flag ? cc->escn_debug_info_alt : cc->escn_debug_info,
+ saved_die_c_offset, cc->barf,
+ "Overrun trace_DIE");
+ VG_(printf)(" <%d><%lx>: Abbrev Number: %llu (%s)%s%s\n",
+ level, posn, (ULong) abbv->abbv_code, ML_(pp_DW_TAG)( dtag ),
+ debug_types_flag ? " (in .debug_types)" : "",
+ alt_flag ? " (in alternate .debug_info)" : "");
nf_i = 0;
while (True) {
DW_AT attr = (DW_AT) abbv->nf[nf_i].at_name;
@@ -1707,10 +1706,24 @@
if (attr == 0 && form == 0) break;
VG_(printf)(" %18s: ", ML_(pp_DW_AT)(attr));
/* Get the form contents, so as to print them */
- get_Form_contents( &cts, cc, c_die, True, form );
+ get_Form_contents( &cts, cc, &c, True, form );
VG_(printf)("\t\n");
}
- VG_(printf)("\n%s:\n", whichparser);
+}
+
+__attribute__((noreturn))
+static void dump_bad_die_and_barf(
+ const HChar *whichparser,
+ DW_TAG dtag,
+ UWord posn,
+ Int level,
+ Cursor* c_die,
+ UWord saved_die_c_offset,
+ g_abbv *abbv,
+ CUConst* cc)
+{
+ trace_DIE (dtag, posn, level, saved_die_c_offset, abbv, cc);
+ VG_(printf)("%s:\n", whichparser);
cc->barf("confused by the above DIE");
}
@@ -3727,9 +3740,12 @@
abbv_code = get_ULEB128( c );
abbv = get_abbv(cc, abbv_code);
atag = abbv->atag;
- TRACE_D3("\n");
- TRACE_D3(" <%d><%lx>: Abbrev Number: %llu (%s)\n",
- level, posn, abbv_code, ML_(pp_DW_TAG)( atag ) );
+
+ if (td3) {
+ TRACE_D3("\n");
+ trace_DIE ((DW_TAG)atag, posn, level,
+ get_position_of_Cursor( c ), abbv, cc);
+ }
if (atag == 0)
cc->barf("read_DIE: invalid zero tag on DIE");
@@ -3811,6 +3827,7 @@
At the same time, establish sibling value if the DIE has one. */
UInt nf_i;
+ TRACE_D3(" (skipped DIE)\n");
nf_i = 0;
while (True) {
FormContents cts;
@@ -3818,16 +3835,12 @@
ULong at_form = abbv->nf[nf_i].at_form;
nf_i++;
if (at_name == 0 && at_form == 0) break;
- TRACE_D3(" %18s: ", ML_(pp_DW_AT)(at_name));
/* Get the form contents, but ignore them; the only purpose is
- to print them, if td3 is True, and skip the data. */
- get_Form_contents( &cts, cc, c, td3, (DW_FORM)at_form );
- /* Except that we remember if this DIE has a sibling. */
+ to skip the data or get the DIE sibling, if it has one. */
+ get_Form_contents( &cts, cc, c, False /*td3*/, (DW_FORM)at_form );
if (UNLIKELY(at_name == DW_AT_sibling && cts.szB > 0)) {
sibling = cts.u.val;
}
- TRACE_D3("\t");
- TRACE_D3("\n");
}
}
@@ -3849,7 +3862,7 @@
if (0) TRACE_D3("END children of level %d\n", level);
} else {
// We can skip the childrens, by jumping to the sibling
- TRACE_D3("SKIPPING DIE's children,"
+ TRACE_D3(" SKIPPING DIE's children,"
"jumping to sibling <%d><%lx>\n",
level, sibling);
set_position_of_Cursor( c, sibling );
|
|
From: Siddharth N. <sn...@dr...> - 2014-06-17 05:57:26
|
On 17 June 2014 00:51, Philippe Waroquiers <phi...@sk...> wrote: > On Mon, 2014-06-16 at 22:27 -0400, Siddharth Nilakantan wrote: > > Thanks Philippe. After some investigation, I believe what you > > mentioned is happening exactly. My secondary maps in the shadow memory > > are sized at 2.5MB in the particular example we were discussing. This > > would result in 4MB block sizes being allocated by the VG_arena_malloc > > function. > > > No matter what the payload size, is it always going to alloc at 4MB > > chunks? > It will always mmap superblocks of 4MB or more (in case a > malloc > 4Mb is requested). > > > Does the pszB_to_bszB always return 4MB? > IIRC, pszB_to_bszB is for calculating the usable size of a malloc-ed > block, not used for a mmap-ed superblock. > > > I assume not, because the numbers from profile-heap don't add up > > otherwise. Below is an example just before the tool died: > I think you are confusing malloc-ed blocks with mmap-ed superblocks. > > Ah yes, sorry, I got confused when reading the code. Every malloc does not necessarily lead to a new superblock. In my case, just the requests for a Secondary map entry necessarily resulted in a new superblock. A quick calculation, 7512 sec map entries * (4MB - 2.5MB) = 11GB is very close to the difference I see between VMSpace usage and allocated bytes (29G - 18G). > > > --26681-- tool : 31516000256/31516000256 max/curr mmap'd, 0/0 > > unsplit/split sb unmmap'd, 19706049824/19706049824 max/curr, > > 20929/19706065264 totalloc-blocks/bytes, 28217271 searches > totalloc is the sum of all blocks that have been allocated, some of > these blocks have been freed (very few in your case). > > > > > > -------- Arena "tool": 31516000256/31516000256 max/curr mmap'd, 0/0 > > unsplit/split sb unmmap'd, 19706049824/19706049824 max/curr on_loan > > -------- > > 16 in 1: sched_lock > > 64 in 1: cl.threads.nes.1 > > 80 in 1: cl.init_funcarray.sys.3 > > 80 in 1: cl.clo.nf.1 > > 96 in 1: cl.dump.init_dumps.1 > > 96 in 2: hashtable.Hc.1 > > 112 in 1: options.efn.1 > > 128 in 1: cl.dump.init_dumps.2 > > 144 in 5: cl.events.group.1 > > 160 in 2: commandline.sua.3 > > 160 in 1: cl.events.geMapping.1 > > 208 in 1: cl.init_funcarray.sys.4 > > 208 in 2: commandline.sua.2 > > 208 in 1: cl.threads.nt.1 > > 256 in 1: initimg-linux.sce.5 > > 400 in 7: cl.fn.non.2 > > 448 in 7: cl.events.eventset.1 > > 592 in 2: cl.clo.nc.1 > > 640 in 13: cl.fn.nfn.2 > > 3,840 in 8: cl.fn.non.1 > > 4,000 in 1: cl.context.ifs.1 > > 5,728 in 223: cl.fn.nfnnd.2 > > 9,568 in 13: cl.fn.nfn.1 > > 10,368 in 162: cl.funcinfo.gc.1 > > 12,320 in 2: hashtable.Hc.2 > > 17,840 in 223: cl.fn.nfnnd.1 > > 20,304 in 1: cl.context.ict.1 > > 28,000 in 1: cl.callstack.ics.1 > > 29,824 in 466: cl.jumps.nj.1 > > 35,504 in 1: cl.jumps.ijh.1 > > 40,288 in 1: cl.fn.gfe.1 > > 58,704 in 3,667: cl.bbcc.nr.1 > > 67,504 in 1: cl.bb.ibh.1 > > 80,080 in 1: cl.drwinit_thread.gc.1 > > 80,080 in 1: cl.init_funcarray.sys.2 > > 83,504 in 1: cl.bbcc.ibh.1 > > 240,000 in 1: cl.init_funcarray.sys.1 > > 259,200 in 162: cl.funccontext.gc.1 > > 467,376 in 2,053: cl.bb.nb.1 > > 475,072 in 571: cl.context.nc.1 > > 521,712 in 3,752: cl.bbcc.nb.1 > > 1,581,056 in 3: cl.sim.cs_ic.1 > > 1,600,064 in 2: cl.costs.gc.1 > > 2,621,440 in 1: cl.init_funcarray.sm.1 > > 5,435,072 in 2,016: cl.funcinst.gc.1 > > 19,692,257,280 in 7,512: cl.copy_for_writing.sm.1 -----> Secondary > > Map allocations > > > > > > As we can see, for the tool the "totalloc-blocks" are 20929, with its > > bytes at about 18.3G. > totalloc-blocks are malloc-ed blocks, not mmap-ed superblocks. > > > 20929 * 4MB is a very large number and much greater than even 29G > > which is the reported size of the entire "tool" arena. > > Looking at the details for the "tool" arena and counting the total > > number of allocations, I see 20897 allocations, almost the same as > > 20929 shown at the top. The allocations are dominated by my Secondary > > Map. I'm guessing that fixing the size of the Secondary Maps to > > something that 'aligns' well with 4MB (2.5MB does pretty terribly) > > will reduce the mismatch between VMSpace and counted bytes allocated. > > Do you concur? > Yes these 2.5 MB blocks are very probably the problem. > So, either you choose a better size, or alternatively rather than using > VG_(malloc), you use mmap. See pub_tool_aspacemgr.h about how to get > memory with mmap, for example you could call VG_(am_shadow_alloc) > > Thanks very much. Any special considerations when using Valgrind's mmap? I'll try a few things and report if this solves the problem. > Philippe > > > > |
|
From: Philippe W. <phi...@sk...> - 2014-06-17 05:07:26
|
valgrind revision: 14049 VEX revision: 2878 C compiler: gcc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8) GDB: GNU gdb (GDB) Fedora (7.5.1-37.fc18) Assembler: GNU assembler version 2.23.51.0.1-7.fc18 20120806 C library: GNU C Library stable release version 2.16 uname -mrs: Linux 3.8.8-202.fc18.ppc64p7 ppc64 Vendor version: Fedora release 18 (Spherical Cow) Nightly build on gcc110 ( Fedora release 18 (Spherical Cow), ppc64 ) Started at 2014-06-16 20:00:11 PDT Ended at 2014-06-16 22:04:02 PDT 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 == 584 tests, 9 stderr failures, 3 stdout failures, 0 stderrB failures, 0 stdoutB failures, 2 post failures == memcheck/tests/linux/getregset (stdout) memcheck/tests/linux/getregset (stderr) memcheck/tests/ppc64/power_ISA2_05 (stdout) memcheck/tests/supp_unknown (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/vbit-test/vbit-test (stderr) memcheck/tests/wrap8 (stdout) memcheck/tests/wrap8 (stderr) massif/tests/big-alloc (post) massif/tests/deep-D (post) helgrind/tests/pth_cond_destroy_busy (stderr) helgrind/tests/tc06_two_races_xml (stderr) helgrind/tests/tc18_semabuse (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.26s no: 1.7s ( 6.6x, -----) me: 3.1s (12.0x, -----) ca:20.5s (78.9x, -----) he: 1.8s ( 6.8x, -----) ca: 5.3s (20.5x, -----) dr: 1.7s ( 6.5x, -----) ma: 2.1s ( 8.2x, -----) bigcode1 valgrind-old:0.26s no: 1.7s ( 6.6x, 0.6%) me: 2.8s (10.9x, 9.6%) ca:20.3s (78.2x, 0.9%) he: 1.8s ( 6.8x, 0.0%) ca: 5.5s (21.2x, -3.2%) dr: 1.7s ( 6.5x, 0.0%) ma: 2.1s ( 8.2x, -0.5%) -- bigcode2 -- bigcode2 valgrind-new:0.23s no: 1.5s ( 6.7x, -----) me: 3.0s (12.8x, -----) ca:20.6s (89.8x, -----) he: 2.4s (10.3x, -----) ca: 5.6s (24.5x, -----) dr: 1.9s ( 8.3x, -----) ma: 2.1s ( 9.3x, -----) bigcode2 valgrind-old:0.23s no: 1.5s ( 6.7x, 0.0%) me: 3.2s (13.8x, -7.8%) ca:20.7s (90.0x, -0.2%) he: 2.1s ( 9.2x, 10.2%) ca: 5.5s (23.7x, 3.0%) dr: 1.9s ( 8.0x, 2.6%) ma: 2.1s ( 9.3x, 0.5%) -- bz2 -- bz2 valgrind-new:0.73s no: 4.5s ( 6.2x, -----) me:11.5s (15.8x, -----) ca:28.5s (39.1x, -----) he:14.8s (20.3x, -----) ca:24.5s (33.5x, -----) dr:19.1s (26.2x, -----) ma: 4.7s ( 6.4x, -----) bz2 valgrind-old:0.73s no: 4.5s ( 6.2x, 0.0%) me:11.5s (15.8x, -0.1%) ca:28.6s (39.2x, -0.2%) he:14.8s (20.3x, 0.0%) ca:24.9s (34.1x, -1.6%) dr:19.2s (26.3x, -0.5%) ma: 5.0s ( 6.8x, -6.7%) -- fbench -- fbench valgrind-new:0.34s no: 2.1s ( 6.2x, -----) me: 5.2s (15.2x, -----) ca: 9.1s (26.9x, -----) he: 5.5s (16.1x, -----) ca: 7.9s (23.1x, -----) dr: 4.8s (14.2x, -----) ma: 2.1s ( 6.3x, -----) fbench valgrind-old:0.34s no: 2.1s ( 6.3x, -1.9%) me: 5.2s (15.4x, -1.2%) ca: 9.0s (26.4x, 1.6%) he: 5.3s (15.5x, 3.5%) ca: 7.5s (22.1x, 4.3%) dr: 4.8s (14.2x, 0.0%) ma: 2.1s ( 6.3x, 0.0%) -- ffbench -- ffbench valgrind-new:0.44s no: 1.3s ( 3.0x, -----) me: 2.4s ( 5.4x, -----) ca: 2.7s ( 6.2x, -----) he: 7.1s (16.1x, -----) ca: 7.2s (16.3x, -----) dr: 5.0s (11.5x, -----) ma: 1.1s ( 2.5x, -----) ffbench valgrind-old:0.44s no: 1.4s ( 3.2x, -6.8%) me: 2.7s ( 6.1x,-13.6%) ca: 2.9s ( 6.5x, -4.8%) he: 6.9s (15.8x, 2.3%) ca: 7.5s (17.2x, -5.4%) dr: 5.0s (11.3x, 1.6%) ma: 1.1s ( 2.4x, 1.8%) -- heap -- heap valgrind-new:0.40s no: 2.5s ( 6.2x, -----) me: 9.8s (24.6x, -----) ca:14.9s (37.2x, -----) he:12.0s (29.9x, -----) ca:12.7s (31.7x, -----) dr: 8.2s (20.4x, -----) ma: 8.8s (22.1x, -----) heap valgrind-old:0.40s no: 2.4s ( 6.0x, 3.2%) me: 9.8s (24.6x, -0.1%) ca:14.3s (35.7x, 4.0%) he:11.9s (29.8x, 0.3%) ca:12.1s (30.2x, 4.7%) dr: 8.0s (20.0x, 2.0%) ma: 8.6s (21.5x, 2.8%) -- heap_pdb4 -- heap_pdb4 valgrind-new:0.42s no: 2.6s ( 6.2x, -----) me:13.6s (32.3x, -----) ca:15.2s (36.3x, -----) he:13.4s (31.9x, -----) ca:13.5s (32.1x, -----) dr: 8.9s (21.2x, -----) ma: 8.7s (20.8x, -----) heap_pdb4 valgrind-old:0.42s no: 2.8s ( 6.6x, -6.1%) me:13.8s (32.9x, -2.1%) ca:15.3s (36.3x, -0.1%) he:13.3s (31.6x, 1.0%) ca:13.1s (31.3x, 2.5%) dr: 8.9s (21.1x, 0.1%) ma: 9.0s (21.3x, -2.5%) -- many-loss-records -- many-loss-records valgrind-new:0.03s no: 0.6s (18.7x, -----) me: 2.2s (73.7x, -----) ca: 2.1s (69.3x, -----) he: 1.9s (62.0x, -----) ca: 2.0s (65.3x, -----) dr: 1.6s (52.7x, -----) ma: 1.6s (53.7x, -----) many-loss-records valgrind-old:0.03s no: 0.5s (18.0x, 3.6%) me: 2.2s (74.0x, -0.5%) ca: 2.1s (69.3x, 0.0%) he: 1.9s (62.7x, -1.1%) ca: 2.0s (65.3x, 0.0%) dr: 1.6s (52.7x, 0.0%) ma: 1.6s (53.0x, 1.2%) -- many-xpts -- many-xpts valgrind-new:0.07s no: 0.8s (11.3x, -----) me: 3.4s (48.9x, -----) ca: 5.1s (73.4x, -----) he: 5.0s (71.4x, -----) ca: 3.0s (43.4x, -----) dr: 2.3s (33.4x, -----) ma: 2.3s (32.4x, -----) many-xpts valgrind-old:0.07s no: 0.8s (10.9x, 3.8%) me: 3.4s (48.4x, 0.9%) ca: 5.1s (72.3x, 1.6%) he: 5.0s (70.7x, 1.0%) ca: 3.0s (43.0x, 1.0%) dr: 2.3s (33.4x, 0.0%) ma: 2.4s (33.7x, -4.0%) -- sarp -- sarp valgrind-new:0.02s no: 0.4s (21.5x, -----) me: 3.2s (159.0x, -----) ca: 3.1s (156.0x, -----) he:11.2s (559.0x, -----) ca: 1.7s (84.5x, -----) dr: 1.1s (54.0x, -----) ma: 0.4s (21.5x, -----) sarp valgrind-old:0.02s no: 0.4s (20.0x, 7.0%) me: 3.0s (152.5x, 4.1%) ca: 3.1s (154.5x, 1.0%) he:11.1s (554.5x, 0.8%) ca: 1.9s (97.0x,-14.8%) dr: 1.1s (55.0x, -1.9%) ma: 0.5s (22.5x, -4.7%) -- tinycc -- tinycc valgrind-new:0.27s no: 3.0s (11.1x, -----) me:13.7s (50.8x, -----) ca:18.4s (68.0x, -----) he:19.1s (70.7x, -----) ca:15.7s (58.0x, -----) dr:12.0s (44.4x, -----) ma: 3.8s (14.1x, -----) tinycc valgrind-old:0.27s no: 3.0s (11.1x, 0.0%) me:13.7s (50.9x, -0.1%) ca:18.6s (69.0x, -1.4%) he:18.9s (70.0x, 0.9%) ca:15.6s (57.9x, 0.1%) dr:12.0s (44.4x, -0.1%) ma: 3.8s (14.1x, 0.0%) -- Finished tests in perf ---------------------------------------------- == 11 programs, 154 timings ================= real 54m42.236s user 53m47.195s sys 0m18.939s |
|
From: Philippe W. <phi...@sk...> - 2014-06-17 04:51:14
|
On Mon, 2014-06-16 at 22:27 -0400, Siddharth Nilakantan wrote: > Thanks Philippe. After some investigation, I believe what you > mentioned is happening exactly. My secondary maps in the shadow memory > are sized at 2.5MB in the particular example we were discussing. This > would result in 4MB block sizes being allocated by the VG_arena_malloc > function. > No matter what the payload size, is it always going to alloc at 4MB > chunks? It will always mmap superblocks of 4MB or more (in case a malloc > 4Mb is requested). > Does the pszB_to_bszB always return 4MB? IIRC, pszB_to_bszB is for calculating the usable size of a malloc-ed block, not used for a mmap-ed superblock. > I assume not, because the numbers from profile-heap don't add up > otherwise. Below is an example just before the tool died: I think you are confusing malloc-ed blocks with mmap-ed superblocks. > > --26681-- tool : 31516000256/31516000256 max/curr mmap'd, 0/0 > unsplit/split sb unmmap'd, 19706049824/19706049824 max/curr, > 20929/19706065264 totalloc-blocks/bytes, 28217271 searches totalloc is the sum of all blocks that have been allocated, some of these blocks have been freed (very few in your case). > > > -------- Arena "tool": 31516000256/31516000256 max/curr mmap'd, 0/0 > unsplit/split sb unmmap'd, 19706049824/19706049824 max/curr on_loan > -------- > 16 in 1: sched_lock > 64 in 1: cl.threads.nes.1 > 80 in 1: cl.init_funcarray.sys.3 > 80 in 1: cl.clo.nf.1 > 96 in 1: cl.dump.init_dumps.1 > 96 in 2: hashtable.Hc.1 > 112 in 1: options.efn.1 > 128 in 1: cl.dump.init_dumps.2 > 144 in 5: cl.events.group.1 > 160 in 2: commandline.sua.3 > 160 in 1: cl.events.geMapping.1 > 208 in 1: cl.init_funcarray.sys.4 > 208 in 2: commandline.sua.2 > 208 in 1: cl.threads.nt.1 > 256 in 1: initimg-linux.sce.5 > 400 in 7: cl.fn.non.2 > 448 in 7: cl.events.eventset.1 > 592 in 2: cl.clo.nc.1 > 640 in 13: cl.fn.nfn.2 > 3,840 in 8: cl.fn.non.1 > 4,000 in 1: cl.context.ifs.1 > 5,728 in 223: cl.fn.nfnnd.2 > 9,568 in 13: cl.fn.nfn.1 > 10,368 in 162: cl.funcinfo.gc.1 > 12,320 in 2: hashtable.Hc.2 > 17,840 in 223: cl.fn.nfnnd.1 > 20,304 in 1: cl.context.ict.1 > 28,000 in 1: cl.callstack.ics.1 > 29,824 in 466: cl.jumps.nj.1 > 35,504 in 1: cl.jumps.ijh.1 > 40,288 in 1: cl.fn.gfe.1 > 58,704 in 3,667: cl.bbcc.nr.1 > 67,504 in 1: cl.bb.ibh.1 > 80,080 in 1: cl.drwinit_thread.gc.1 > 80,080 in 1: cl.init_funcarray.sys.2 > 83,504 in 1: cl.bbcc.ibh.1 > 240,000 in 1: cl.init_funcarray.sys.1 > 259,200 in 162: cl.funccontext.gc.1 > 467,376 in 2,053: cl.bb.nb.1 > 475,072 in 571: cl.context.nc.1 > 521,712 in 3,752: cl.bbcc.nb.1 > 1,581,056 in 3: cl.sim.cs_ic.1 > 1,600,064 in 2: cl.costs.gc.1 > 2,621,440 in 1: cl.init_funcarray.sm.1 > 5,435,072 in 2,016: cl.funcinst.gc.1 > 19,692,257,280 in 7,512: cl.copy_for_writing.sm.1 -----> Secondary > Map allocations > > > As we can see, for the tool the "totalloc-blocks" are 20929, with its > bytes at about 18.3G. totalloc-blocks are malloc-ed blocks, not mmap-ed superblocks. > 20929 * 4MB is a very large number and much greater than even 29G > which is the reported size of the entire "tool" arena. > Looking at the details for the "tool" arena and counting the total > number of allocations, I see 20897 allocations, almost the same as > 20929 shown at the top. The allocations are dominated by my Secondary > Map. I'm guessing that fixing the size of the Secondary Maps to > something that 'aligns' well with 4MB (2.5MB does pretty terribly) > will reduce the mismatch between VMSpace and counted bytes allocated. > Do you concur? Yes these 2.5 MB blocks are very probably the problem. So, either you choose a better size, or alternatively rather than using VG_(malloc), you use mmap. See pub_tool_aspacemgr.h about how to get memory with mmap, for example you could call VG_(am_shadow_alloc) Philippe |
|
From: Christian B. <bor...@de...> - 2014-06-17 04:08:50
|
valgrind revision: 14049 VEX revision: 2878 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.21-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-06-17 03:45:01 CEST Ended at 2014-06-17 06:08:38 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 == 650 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/vbit-test/vbit-test (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.22s no: 4.3s (19.6x, -----) me: 6.9s (31.3x, -----) ca:26.3s (119.7x, -----) he: 5.0s (23.0x, -----) ca: 9.1s (41.5x, -----) dr: 5.4s (24.5x, -----) ma: 5.0s (22.5x, -----) bigcode1 valgrind-old:0.22s no: 4.3s (19.6x, 0.2%) me: 6.9s (31.3x, -0.1%) ca:26.4s (119.8x, -0.1%) he: 5.1s (23.1x, -0.8%) ca: 9.2s (41.6x, -0.1%) dr: 5.4s (24.5x, 0.0%) ma: 5.0s (22.5x, 0.2%) -- bigcode2 -- bigcode2 valgrind-new:0.24s no: 7.3s (30.2x, -----) me:13.8s (57.3x, -----) ca:39.4s (164.2x, -----) he:10.1s (42.0x, -----) ca:14.3s (59.4x, -----) dr: 9.6s (39.8x, -----) ma: 8.4s (34.9x, -----) bigcode2 valgrind-old:0.24s no: 7.2s (30.2x, 0.1%) me:13.8s (57.6x, -0.5%) ca:39.5s (164.5x, -0.2%) he:10.1s (41.9x, 0.3%) ca:14.3s (59.5x, -0.1%) dr: 9.5s (39.7x, 0.3%) ma: 8.4s (35.0x, -0.4%) -- bz2 -- bz2 valgrind-new:0.69s no: 5.0s ( 7.2x, -----) me:12.8s (18.5x, -----) ca:30.8s (44.6x, -----) he:19.5s (28.3x, -----) ca:34.3s (49.7x, -----) dr:29.2s (42.3x, -----) ma: 4.7s ( 6.8x, -----) bz2 valgrind-old:0.69s no: 5.0s ( 7.2x, -0.2%) me:12.8s (18.5x, 0.0%) ca:30.6s (44.4x, 0.4%) he:19.6s (28.4x, -0.6%) ca:34.3s (49.7x, 0.0%) dr:29.2s (42.3x, -0.1%) ma: 4.7s ( 6.8x, 0.0%) -- fbench -- fbench valgrind-new:0.40s no: 1.6s ( 4.0x, -----) me: 4.2s (10.6x, -----) ca: 9.3s (23.2x, -----) he: 6.2s (15.5x, -----) ca: 7.2s (18.0x, -----) dr: 5.5s (13.8x, -----) ma: 1.7s ( 4.2x, -----) fbench valgrind-old:0.40s no: 1.6s ( 4.0x, 0.6%) me: 4.2s (10.5x, 0.2%) ca: 9.3s (23.2x, -0.2%) he: 6.2s (15.5x, 0.0%) ca: 7.2s (17.9x, 0.4%) dr: 5.5s (13.8x, -0.0%) ma: 1.7s ( 4.2x, 0.6%) -- ffbench -- ffbench valgrind-new:0.21s no: 1.1s ( 5.0x, -----) me: 3.0s (14.3x, -----) ca: 3.0s (14.4x, -----) he:43.4s (206.5x, -----) ca: 9.6s (45.8x, -----) dr: 6.9s (33.0x, -----) ma: 1.0s ( 4.7x, -----) ffbench valgrind-old:0.21s no: 1.1s ( 5.0x, 0.0%) me: 3.0s (14.3x, 0.0%) ca: 3.0s (14.3x, 0.3%) he:44.2s (210.5x, -1.9%) ca: 9.6s (45.8x, 0.1%) dr: 6.9s (33.0x, 0.0%) ma: 1.0s ( 4.7x, 0.0%) -- heap -- heap valgrind-new:0.23s no: 1.9s ( 8.3x, -----) me: 8.7s (38.0x, -----) ca:13.2s (57.2x, -----) he:12.7s (55.3x, -----) ca:11.3s (49.0x, -----) dr: 7.7s (33.4x, -----) ma: 8.0s (34.8x, -----) heap valgrind-old:0.23s no: 1.9s ( 8.3x, 0.0%) me: 8.8s (38.2x, -0.5%) ca:13.2s (57.3x, -0.2%) he:12.8s (55.7x, -0.5%) ca:11.3s (49.1x, -0.1%) dr: 7.7s (33.6x, -0.5%) ma: 7.9s (34.5x, 0.9%) -- heap_pdb4 -- heap_pdb4 valgrind-new:0.22s no: 2.1s ( 9.4x, -----) me:12.8s (58.3x, -----) ca:14.2s (64.3x, -----) he:14.0s (63.8x, -----) ca:12.3s (56.0x, -----) dr: 8.6s (39.0x, -----) ma: 8.1s (36.9x, -----) heap_pdb4 valgrind-old:0.22s no: 2.1s ( 9.4x, 0.0%) me:13.0s (59.0x, -1.2%) ca:14.2s (64.4x, -0.1%) he:14.1s (64.0x, -0.4%) ca:12.4s (56.2x, -0.2%) dr: 8.7s (39.5x, -1.4%) ma: 8.1s (36.9x, 0.0%) -- many-loss-records -- many-loss-records valgrind-new:0.02s no: 0.5s (24.0x, -----) me: 2.1s (103.5x, -----) ca: 1.9s (97.5x, -----) he: 2.2s (108.5x, -----) ca: 1.9s (96.0x, -----) dr: 1.7s (86.5x, -----) ma: 1.7s (85.0x, -----) many-loss-records valgrind-old:0.02s no: 0.5s (24.5x, -2.1%) me: 2.1s (104.5x, -1.0%) ca: 1.9s (97.0x, 0.5%) he: 2.1s (107.5x, 0.9%) ca: 1.9s (96.0x, 0.0%) dr: 1.7s (87.0x, -0.6%) ma: 1.7s (85.0x, 0.0%) -- many-xpts -- many-xpts valgrind-new:0.07s no: 0.6s ( 9.0x, -----) me: 3.2s (45.1x, -----) ca:372.2s (5317.1x, -----) he: 6.6s (94.4x, -----) ca: 2.8s (39.9x, -----) dr: 2.5s (35.9x, -----) ma: 2.7s (38.7x, -----) many-xpts valgrind-old:0.07s no: 0.6s ( 9.1x, -1.6%) me: 3.2s (45.1x, 0.0%) ca:367.7s (5253.0x, 1.2%) he: 6.5s (92.9x, 1.7%) ca: 2.8s (40.1x, -0.7%) dr: 2.5s (35.9x, 0.0%) ma: 2.7s (38.1x, 1.5%) -- sarp -- sarp valgrind-new:0.02s no: 0.6s (28.0x, -----) me: 3.4s (171.5x, -----) ca: 3.2s (160.5x, -----) he:17.1s (855.0x, -----) ca: 2.0s (102.5x, -----) dr: 1.4s (67.5x, -----) ma: 0.5s (26.0x, -----) sarp valgrind-old:0.02s no: 0.6s (28.5x, -1.8%) me: 3.4s (171.5x, 0.0%) ca: 3.1s (157.5x, 1.9%) he:16.5s (823.0x, 3.7%) ca: 2.1s (103.0x, -0.5%) dr: 1.4s (67.5x, 0.0%) ma: 0.5s (26.0x, 0.0%) -- tinycc -- tinycc valgrind-new:0.22s no: 2.9s (13.3x, -----) me:14.4s (65.6x, -----) ca:30.0s (136.2x, -----) he:28.1s (127.6x, -----) ca:21.3s (96.9x, -----) dr:20.6s (93.5x, -----) ma: 4.1s (18.6x, -----) tinycc valgrind-old:0.22s no: 2.8s (12.7x, 4.8%) me:14.4s (65.7x, -0.1%) ca:30.0s (136.4x, -0.1%) he:27.7s (125.9x, 1.4%) ca:21.4s (97.1x, -0.2%) dr:20.6s (93.5x, 0.0%) ma: 4.1s (18.6x, 0.0%) -- Finished tests in perf ---------------------------------------------- == 11 programs, 154 timings ================= real 110m29.749s user 109m31.843s sys 0m49.226s |
|
From: Tom H. <to...@co...> - 2014-06-17 03:32:59
|
valgrind revision: 14049 VEX revision: 2878 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.13.10-200.fc20.x86_64 x86_64 Vendor version: Fedora release 9 (Sulphur) Nightly build on bristol ( x86_64, Fedora 9 ) Started at 2014-06-17 03:51:14 BST Ended at 2014-06-17 04:32:30 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 == 653 tests, 3 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) memcheck/tests/vbit-test/vbit-test (stderr) none/tests/amd64/sse4-64 (stdout) |
|
From: Rich C. <rc...@wi...> - 2014-06-17 03:12:29
|
valgrind revision: 14049
VEX revision: 2878
C compiler: gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]
GDB: GNU gdb (GDB) SUSE (7.5.1-2.1.1)
Assembler: GNU assembler (GNU Binutils; openSUSE 12.3) 2.23.1
C library: GNU C Library (GNU libc) stable release version 2.17 (git c758a6861537)
uname -mrs: Linux 3.7.9-1.1-desktop x86_64
Vendor version: Welcome to openSUSE 12.3 "Dartmouth" Beta 1 - Kernel %r (%t).
Nightly build on ultra ( gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012] Linux 3.7.9-1.1-desktop x86_64 )
Started at 2014-06-16 21:30:01 CDT
Ended at 2014-06-16 22:12:14 CDT
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
== 677 tests, 1 stderr failure, 0 stdout failures, 2 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/mssnapshot (stderrB)
memcheck/tests/vbit-test/vbit-test (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
== 677 tests, 85 stderr failures, 7 stdout failures, 2 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/mssnapshot (stderrB)
memcheck/tests/dw4 (stderr)
memcheck/tests/varinfo1 (stderr)
memcheck/tests/varinfo2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo4 (stdout)
memcheck/tests/varinfo4 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/varinfo6 (stdout)
memcheck/tests/varinfo6 (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
helgrind/tests/hg03_inherit (stderr)
helgrind/tests/hg04_race (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/rwlock_race (stderr)
helgrind/tests/tc01_simple_race (stderr)
helgrind/tests/tc05_simple_race (stderr)
helgrind/tests/tc06_two_races (stderr)
helgrind/tests/tc06_two_races_xml (stderr)
helgrind/tests/tc16_byterace (stderr)
helgrind/tests/tc20_verifywrap (stderr)
helgrind/tests/tc21_pthonce (stdout)
helgrind/tests/tc21_pthonce (stderr)
drd/tests/annotate_barrier (stderr)
drd/tests/annotate_barrier_xml (stderr)
drd/tests/annotate_hb_err (stderr)
drd/tests/annotate_hbefore (stderr)
drd/tests/annotate_ignore_read (stderr)
drd/tests/annotate_ignore_rw (stderr)
drd/tests/annotate_ignore_rw2 (stderr)
drd/tests/annotate_ignore_write (stderr)
drd/tests/annotate_ignore_write2 (stderr)
drd/tests/annotate_order_1 (stderr)
drd/tests/annotate_order_2 (stderr)
drd/tests/annotate_order_3 (stderr)
drd/tests/annotate_publish_hg (stderr)
drd/tests/annotate_rwlock (stderr)
drd/tests/annotate_rwlock_hg (stderr)
drd/tests/annotate_sem (stderr)
drd/tests/annotate_smart_pointer (stderr)
drd/tests/annotate_smart_pointer2 (stderr)
drd/tests/annotate_spinlock (stderr)
drd/tests/annotate_static (stderr)
drd/tests/annotate_trace_memory (stderr)
drd/tests/annotate_trace_memory_xml (stderr)
drd/tests/atomic_var (stderr)
drd/tests/boost_thread (stderr)
drd/tests/bug-235681 (stderr)
drd/tests/concurrent_close (stderr)
drd/tests/fp_race (stderr)
drd/tests/fp_race_xml (stderr)
drd/tests/free_is_write (stderr)
drd/tests/free_is_write2 (stderr)
drd/tests/hg03_inherit (stderr)
drd/tests/hg04_race (stderr)
drd/tests/hg05_race2 (stderr)
drd/tests/linuxthreads_det (stderr)
drd/tests/pth_cancel_locked (stderr)
drd/tests/pth_cleanup_handler (stderr)
drd/tests/pth_detached2 (stderr)
drd/tests/pth_mutex_reinit (stderr)
drd/tests/pth_once (stderr)
drd/tests/pth_process_shared_mutex (stderr)
drd/tests/pth_spinlock (stderr)
drd/tests/pth_uninitialized_cond (stderr)
drd/tests/recursive_mutex (stderr)
drd/tests/rwlock_race (stderr)
drd/tests/rwlock_test (stderr)
drd/tests/rwlock_type_checking (stderr)
drd/tests/sem_as_mutex (stderr)
drd/tests/sem_as_mutex2 (stderr)
drd/tests/sem_as_mutex3 (stderr)
drd/tests/sem_open (stderr)
drd/tests/sem_open2 (stderr)
drd/tests/sem_open3 (stderr)
drd/tests/sem_open_traced (stderr)
drd/tests/sem_wait (stderr)
drd/tests/tc01_simple_race (stderr)
drd/tests/tc16_byterace (stderr)
drd/tests/tc19_shadowmem (stderr)
drd/tests/tc24_nonzero_sem (stderr)
drd/tests/thread_name (stderr)
drd/tests/thread_name_xml (stderr)
exp-sgcheck/tests/bad_percentify (stdout)
exp-sgcheck/tests/bad_percentify (stderr)
exp-sgcheck/tests/globalerr (stderr)
exp-sgcheck/tests/hackedbz2 (stdout)
exp-sgcheck/tests/hackedbz2 (stderr)
exp-sgcheck/tests/hsg (stdout)
exp-sgcheck/tests/hsg (stderr)
exp-sgcheck/tests/preen_invars (stdout)
exp-sgcheck/tests/preen_invars (stderr)
exp-sgcheck/tests/stackerr (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Mon Jun 16 21:48:08 2014
--- new.short Mon Jun 16 22:12:14 2014
***************
*** 8,104 ****
! == 677 tests, 85 stderr failures, 7 stdout failures, 2 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/mssnapshot (stderrB)
- memcheck/tests/dw4 (stderr)
- memcheck/tests/varinfo1 (stderr)
- memcheck/tests/varinfo2 (stderr)
- memcheck/tests/varinfo3 (stderr)
- memcheck/tests/varinfo4 (stdout)
- memcheck/tests/varinfo4 (stderr)
- memcheck/tests/varinfo5 (stderr)
- memcheck/tests/varinfo6 (stdout)
- memcheck/tests/varinfo6 (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
- helgrind/tests/hg03_inherit (stderr)
- helgrind/tests/hg04_race (stderr)
- helgrind/tests/hg05_race2 (stderr)
- helgrind/tests/rwlock_race (stderr)
- helgrind/tests/tc01_simple_race (stderr)
- helgrind/tests/tc05_simple_race (stderr)
- helgrind/tests/tc06_two_races (stderr)
- helgrind/tests/tc06_two_races_xml (stderr)
- helgrind/tests/tc16_byterace (stderr)
- helgrind/tests/tc20_verifywrap (stderr)
- helgrind/tests/tc21_pthonce (stdout)
- helgrind/tests/tc21_pthonce (stderr)
- drd/tests/annotate_barrier (stderr)
- drd/tests/annotate_barrier_xml (stderr)
- drd/tests/annotate_hb_err (stderr)
- drd/tests/annotate_hbefore (stderr)
- drd/tests/annotate_ignore_read (stderr)
- drd/tests/annotate_ignore_rw (stderr)
- drd/tests/annotate_ignore_rw2 (stderr)
- drd/tests/annotate_ignore_write (stderr)
- drd/tests/annotate_ignore_write2 (stderr)
- drd/tests/annotate_order_1 (stderr)
- drd/tests/annotate_order_2 (stderr)
- drd/tests/annotate_order_3 (stderr)
- drd/tests/annotate_publish_hg (stderr)
- drd/tests/annotate_rwlock (stderr)
- drd/tests/annotate_rwlock_hg (stderr)
- drd/tests/annotate_sem (stderr)
- drd/tests/annotate_smart_pointer (stderr)
- drd/tests/annotate_smart_pointer2 (stderr)
- drd/tests/annotate_spinlock (stderr)
- drd/tests/annotate_static (stderr)
- drd/tests/annotate_trace_memory (stderr)
- drd/tests/annotate_trace_memory_xml (stderr)
- drd/tests/atomic_var (stderr)
- drd/tests/boost_thread (stderr)
- drd/tests/bug-235681 (stderr)
- drd/tests/concurrent_close (stderr)
- drd/tests/fp_race (stderr)
- drd/tests/fp_race_xml (stderr)
- drd/tests/free_is_write (stderr)
- drd/tests/free_is_write2 (stderr)
- drd/tests/hg03_inherit (stderr)
- drd/tests/hg04_race (stderr)
- drd/tests/hg05_race2 (stderr)
- drd/tests/linuxthreads_det (stderr)
- drd/tests/pth_cancel_locked (stderr)
- drd/tests/pth_cleanup_handler (stderr)
- drd/tests/pth_detached2 (stderr)
- drd/tests/pth_mutex_reinit (stderr)
- drd/tests/pth_once (stderr)
- drd/tests/pth_process_shared_mutex (stderr)
- drd/tests/pth_spinlock (stderr)
- drd/tests/pth_uninitialized_cond (stderr)
- drd/tests/recursive_mutex (stderr)
- drd/tests/rwlock_race (stderr)
- drd/tests/rwlock_test (stderr)
- drd/tests/rwlock_type_checking (stderr)
- drd/tests/sem_as_mutex (stderr)
- drd/tests/sem_as_mutex2 (stderr)
- drd/tests/sem_as_mutex3 (stderr)
- drd/tests/sem_open (stderr)
- drd/tests/sem_open2 (stderr)
- drd/tests/sem_open3 (stderr)
- drd/tests/sem_open_traced (stderr)
- drd/tests/sem_wait (stderr)
- drd/tests/tc01_simple_race (stderr)
- drd/tests/tc16_byterace (stderr)
- drd/tests/tc19_shadowmem (stderr)
- drd/tests/tc24_nonzero_sem (stderr)
- drd/tests/thread_name (stderr)
- drd/tests/thread_name_xml (stderr)
- exp-sgcheck/tests/bad_percentify (stdout)
- exp-sgcheck/tests/bad_percentify (stderr)
- exp-sgcheck/tests/globalerr (stderr)
- exp-sgcheck/tests/hackedbz2 (stdout)
- exp-sgcheck/tests/hackedbz2 (stderr)
- exp-sgcheck/tests/hsg (stdout)
- exp-sgcheck/tests/hsg (stderr)
- exp-sgcheck/tests/preen_invars (stdout)
- exp-sgcheck/tests/preen_invars (stderr)
- exp-sgcheck/tests/stackerr (stderr)
--- 8,13 ----
! == 677 tests, 1 stderr failure, 0 stdout failures, 2 stderrB failures, 0 stdoutB failures, 0 post failures ==
gdbserver_tests/hginfo (stderrB)
gdbserver_tests/mssnapshot (stderrB)
memcheck/tests/vbit-test/vbit-test (stderr)
=================================================
./valgrind-new/gdbserver_tests/hginfo.stderrB.diff
=================================================
--- hginfo.stderrB.exp 2014-06-16 21:52:08.018571595 -0500
+++ hginfo.stderrB.out 2014-06-16 22:00:53.191190228 -0500
@@ -1,5 +1,11 @@
relaying data between gdb and process ....
+Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2
+Try: zypper install -C "debuginfo(build-id)=ecb8ef1a6904a2a3ec60a527f415f520c8636158"
vgdb-error value changed from 0 to 999999
+Missing separate debuginfo for /lib64/libpthread.so.0
+Try: zypper install -C "debuginfo(build-id)=ef5f5dbcb2398c608fef7884e1bfb65be3b5f0ef"
+Missing separate debuginfo for /lib64/libc.so.6
+Try: zypper install -C "debuginfo(build-id)=bd1473e8e6a4c10a14731b5be4b35b4e87db2af7"
Lock ga 0x........ {
Address 0x........ is 0 bytes inside data symbol "mx"
kind mbRec
=================================================
./valgrind-new/gdbserver_tests/mssnapshot.stderrB.diff
=================================================
--- mssnapshot.stderrB.exp 2014-06-16 21:52:08.000572109 -0500
+++ mssnapshot.stderrB.out 2014-06-16 22:01:24.898321909 -0500
@@ -1,5 +1,11 @@
relaying data between gdb and process ....
+Missing separate debuginfo for /lib64/ld-linux-x86-64.so.2
+Try: zypper install -C "debuginfo(build-id)=ecb8ef1a6904a2a3ec60a527f415f520c8636158"
vgdb-error value changed from 0 to 999999
+Missing separate debuginfo for /lib64/libpthread.so.0
+Try: zypper install -C "debuginfo(build-id)=ef5f5dbcb2398c608fef7884e1bfb65be3b5f0ef"
+Missing separate debuginfo for /lib64/libc.so.6
+Try: zypper install -C "debuginfo(build-id)=bd1473e8e6a4c10a14731b5be4b35b4e87db2af7"
general valgrind monitor commands:
help [debug] : monitor command help. With debug: + debugging commands
v.wait [<ms>] : sleep <ms> (default 0) then continue
=================================================
./valgrind-new/memcheck/tests/vbit-test/vbit-test.stderr.diff
=================================================
--- vbit-test.stderr.exp 2014-06-16 21:49:25.901010704 -0500
+++ vbit-test.stderr.out 2014-06-16 22:04:24.183411980 -0500
@@ -0,0 +1 @@
+unknown opcode 5824
=================================================
./valgrind-old/drd/tests/annotate_barrier.stderr.diff
=================================================
--- annotate_barrier.stderr.exp 2014-06-16 21:31:02.538218355 -0500
+++ annotate_barrier.stderr.out 2014-06-16 21:46:35.925664812 -0500
@@ -1,47 +1,23 @@
-The annotation macro ANNOTATE_BARRIER_INIT has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_init (annotate_barrier.c:?)
- by 0x........: barriers_and_races (annotate_barrier.c:?)
- by 0x........: main (annotate_barrier.c:?)
-
-Thread 2:
-The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-Thread 3:
-The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-Thread 2:
-Conflicting store by thread 2 at 0x........ size 4
- at 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
- by 0x........: (within libpthread-?.?.so)
-Address 0x........ is at offset 0 from 0x......... Allocation context:
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: barriers_and_races (annotate_barrier.c:?)
- by 0x........: main (annotate_barrier.c:?)
-
-The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-Thread 1:
-The annotation macro ANNOTATE_BARRIER_DESTROY has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_destroy (annotate_barrier.c:?)
- by 0x........: barriers_and_races (annotate_barrier.c:?)
- by 0x........: main (annotate_barrier.c:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 11 errors from 7 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_barrier_xml.stderr.diff
=================================================
--- annotate_barrier_xml.stderr.exp 2014-06-16 21:31:02.479219970 -0500
+++ annotate_barrier_xml.stderr.out 2014-06-16 21:46:35.985663168 -0500
@@ -26,302 +26,26 @@
</argv>
</args>
-<status>
- <state>RUNNING</state>
- <time>...</time>
-</status>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <kind>UnimpDrdClReq</kind>
- <what>The annotation macro ANNOTATE_BARRIER_INIT has not yet been implemented in <valgrind/drd.h></what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barrier_init</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barriers_and_races</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- </stack>
-</error>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <kind>UnimpDrdClReq</kind>
- <what>The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h></what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barrier_wait</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>threadfunc</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>vgDrd_thread_wrapper</fn>
- <dir>...</dir>
- <file>drd_pthread_intercepts.c</file>
- <line>...</line>
- </frame>
- </stack>
-</error>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <kind>UnimpDrdClReq</kind>
- <what>The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h></what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barrier_wait</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>threadfunc</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
<truncated beyond 100 lines>
=================================================
./valgrind-old/drd/tests/annotate_hb_err.stderr.diff
=================================================
--- annotate_hb_err.stderr.exp 2014-06-16 21:31:02.477220025 -0500
+++ annotate_hb_err.stderr.out 2014-06-16 21:46:36.043661581 -0500
@@ -1,25 +1,23 @@
-wrong type of synchronization object
- at 0x........: U_AnnotateHappensBefore (unified_annotations.h:?)
- by 0x........: main (annotate_hb_err.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (annotate_hb_err.c:?)
-
-wrong type of synchronization object
- at 0x........: U_AnnotateHappensBefore (unified_annotations.h:?)
- by 0x........: main (annotate_hb_err.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (annotate_hb_err.c:?)
-
-wrong type of synchronization object
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (annotate_hb_err.c:?)
-order annotation 0x........ was first observed at:
- at 0x........: U_AnnotateHappensAfter (unified_annotations.h:?)
- by 0x........: main (annotate_hb_err.c:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_hbefore.stderr.diff
=================================================
--- annotate_hbefore.stderr.exp 2014-06-16 21:31:02.462220435 -0500
+++ annotate_hbefore.stderr.out 2014-06-16 21:46:36.597646412 -0500
@@ -1,3 +1,23 @@
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_ignore_read.stderr.diff
=================================================
--- annotate_ignore_read.stderr.exp 2014-06-16 21:31:02.473220134 -0500
+++ annotate_ignore_read.stderr.out 2014-06-16 21:46:36.657644770 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test69: negative
- GLOB=30
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_ignore_rw.stderr.diff
=================================================
--- annotate_ignore_rw.stderr.exp 2014-06-16 21:31:02.489219696 -0500
+++ annotate_ignore_rw.stderr.out 2014-06-16 21:46:36.710643319 -0500
@@ -1,9 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_rw.c:12
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_ignore_rw2.stderr.diff
=================================================
--- annotate_ignore_rw2.stderr.exp 2014-06-16 21:31:02.520218848 -0500
+++ annotate_ignore_rw2.stderr.out 2014-06-16 21:46:36.749642251 -0500
@@ -1,19 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_b"
-declared at annotate_ignore_rw.c:11
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_rw.c:10
-
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_rw.c:12
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_ignore_write.stderr.diff
=================================================
--- annotate_ignore_write.stderr.exp 2014-06-16 21:31:02.503219313 -0500
+++ annotate_ignore_write.stderr.out 2014-06-16 21:46:36.790641128 -0500
@@ -1,19 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_b"
-declared at annotate_ignore_write.c:11
-
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_write.c:12
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_write.c:10
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_ignore_write2.stderr.diff
=================================================
--- annotate_ignore_write2.stderr.exp 2014-06-16 21:31:02.439221087 -0500
+++ annotate_ignore_write2.stderr.out 2014-06-16 21:46:36.828640087 -0500
@@ -1,24 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_b"
-declared at annotate_ignore_write.c:11
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_write.c:10
-
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_write.c:12
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_write.c:10
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_order_1.stderr.diff
=================================================
--- annotate_order_1.stderr.exp 2014-06-16 21:31:02.459220517 -0500
+++ annotate_order_1.stderr.out 2014-06-16 21:46:36.874638828 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test03: negative
- GLOB=2
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_order_2.stderr.diff
=================================================
--- annotate_order_2.stderr.exp 2014-06-16 21:31:02.541218273 -0500
+++ annotate_order_2.stderr.out 2014-06-16 21:46:36.920637568 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test30: negative
- GLOB=47
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_order_3.stderr.diff
=================================================
--- annotate_order_3.stderr.exp 2014-06-16 21:31:02.504219286 -0500
+++ annotate_order_3.stderr.out 2014-06-16 21:46:36.968636254 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test31: negative
- GLOB=48
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_publish_hg.stderr.diff
=================================================
--- annotate_publish_hg.stderr.exp 2014-06-16 21:31:02.466220326 -0500
+++ annotate_publish_hg.stderr.out 2014-06-16 21:46:37.005635241 -0500
@@ -1,7 +1,23 @@
-The annotation macro ANNOTATE_PUBLISH_MEMORY_RANGE has not yet been implemented in <valgrind/helgrind.h>
- at 0x........: main (annotate_publish_hg.c:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_rwlock.stderr.diff
=================================================
--- annotate_rwlock.stderr.exp 2014-06-16 21:31:02.498219450 -0500
+++ annotate_rwlock.stderr.out 2014-06-16 21:46:37.047634092 -0500
@@ -1,4 +1,23 @@
-Finished.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_rwlock_hg.stderr.diff
=================================================
--- annotate_rwlock_hg.stderr.exp 2014-06-16 21:31:02.514219012 -0500
+++ annotate_rwlock_hg.stderr.out 2014-06-16 21:46:37.068633516 -0500
@@ -1 +0,0 @@
-Total error count is below threshold.
=================================================
./valgrind-old/drd/tests/annotate_sem.stderr.diff
=================================================
--- annotate_sem.stderr.exp 2014-06-16 21:31:02.521218820 -0500
+++ annotate_sem.stderr.out 2014-06-16 21:46:37.110632367 -0500
@@ -1,4 +1,23 @@
-Finished.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_smart_pointer.stderr.diff
=================================================
--- annotate_smart_pointer.stderr.exp 2014-06-16 21:31:02.449220792 -0500
+++ annotate_smart_pointer.stderr.out 2014-06-16 21:46:37.156631107 -0500
@@ -1,4 +1,23 @@
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_smart_pointer2.stderr.diff
=================================================
--- annotate_smart_pointer2.stderr.exp 2014-06-16 21:31:02.446220875 -0500
+++ annotate_smart_pointer2.stderr.out 2014-06-16 21:46:37.225629218 -0500
@@ -1,13 +1,23 @@
-Conflicting store by thread x at 0x........ size 4
- at 0x........: counter::~counter() (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::set(counter*, AtomicInt32*) (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::operator=(counter*) (annotate_smart_pointer.cpp:?)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Address 0x........ is at offset ... from 0x......... Allocation context:
- at 0x........: ...operator new... (vg_replace_malloc.c:...)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_smart_pointer2.stderr.diff-darwin
=================================================
--- annotate_smart_pointer2.stderr.exp-darwin 2014-06-16 21:31:02.510219121 -0500
+++ annotate_smart_pointer2.stderr.out 2014-06-16 21:46:37.225629218 -0500
@@ -1,14 +1,23 @@
-Conflicting store by thread x at 0x........ size 4
- at 0x........: counter::~counter() (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::set(counter*, AtomicInt32*) (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::operator=(counter*) (annotate_smart_pointer.cpp:?)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Address 0x........ is at offset ... from 0x......... Allocation context:
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: operator new(unsigned long) (in /usr/lib/libstdc++.6.0.9.dylib)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_spinlock.stderr.diff
=================================================
--- annotate_spinlock.stderr.exp 2014-06-16 21:31:02.440221052 -0500
+++ annotate_spinlock.stderr.out 2014-06-16 21:46:37.279627739 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test27: negative
- GLOB=4
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_static.stderr.diff
=================================================
--- annotate_static.stderr.exp 2014-06-16 21:31:02.455220627 -0500
+++ annotate_static.stderr.out 2014-06-16 21:46:37.328626398 -0500
@@ -1,4 +1,23 @@
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_trace_memory.stderr.diff-32bit
=================================================
--- annotate_trace_memory.stderr.exp-32bit 2014-06-16 21:31:02.471220189 -0500
+++ annotate_trace_memory.stderr.out 2014-06-16 21:46:37.415624015 -0500
@@ -1,52 +1,23 @@
-float
-store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-double
-store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 8 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint8_t
-store 0x........ size 1 val 5/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 1 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 1 val 11/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint16_t
-store 0x........ size 2 val 7/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 2 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 2 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint32_t
-store 0x........ size 4 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint64_t
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 305419905/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_trace_memory.stderr.diff-64bit
=================================================
--- annotate_trace_memory.stderr.exp-64bit 2014-06-16 21:31:02.486219778 -0500
+++ annotate_trace_memory.stderr.out 2014-06-16 21:46:37.415624015 -0500
@@ -1,46 +1,23 @@
-float
-store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-double
-store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 8 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint8_t
-store 0x........ size 1 val 5/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 1 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 1 val 11/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint16_t
-store 0x........ size 2 val 7/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 2 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 2 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint32_t
-store 0x........ size 4 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint64_t
-store 0x........ size 8 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 8 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 8 val 305419905/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_trace_memory.stderr.diff-mips32
=================================================
--- annotate_trace_memory.stderr.exp-mips32 2014-06-16 21:31:02.505219258 -0500
+++ annotate_trace_memory.stderr.out 2014-06-16 21:46:37.415624015 -0500
@@ -1,58 +1,23 @@
-float
-store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-double
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1074266112/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1075576832/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint8_t
-store 0x........ size 1 val 5/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 1 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 1 val 11/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint16_t
-store 0x........ size 2 val 7/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 2 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 2 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint32_t
-store 0x........ size 4 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint64_t
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 305419905/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /home/coe/src/vg/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_trace_memory_xml.stderr.diff-32bit
=================================================
--- annotate_trace_memory_xml.stderr.exp-32bit 2014-06-16 21:31:02.523218766 -0500
+++ annotate_trace_memory_xml.stderr.out 2014-06-16 21:46:37.469622537 -0500
@@ -23,280 +23,26 @@
</argv>
</args>
-<status>
- <state>RUNNING</state>
- <time>...</time>
-</status>
+</valgrindoutput>
-float
- <trace><text>store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
- <trace><text>load 0x........ size 4 (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
- <trace><text>store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
-double
- <trace><text>store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
- <trace><text>load 0x........ size 8 (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
- <trace><text>store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
-uint8_t
- <trace><text>store 0x........ size 1 val 5/0x........ (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
- <trace><text>load 0x........ size 1 (thread x / vc ...)</text>
<truncated beyond 100 lines>
=================================================
./valgrind-old/drd/tests/annotate_trace_memory_xml.stderr.diff-64bit
=================================================
--- annotate_trace_memory_xml.stderr.exp-64bit 2014-06-16 21:31:02.540218300 -0500
+++ annotate_trace_memory_xml.stderr.out 2014-06-16 21:46:37.469622537 -0500
@@ -23,244 +23,26 @@
</argv>
</args>
-<status>
- <state>RUNNING</state>
- <time>...</time>
-</status>
-
-float
- <trace><text>store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stack>
- </trace>
- <trace><text>load 0x........ size 4 (thread x / vc ...)</text>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_trace_memory.c</file>
- <line>...</line>
- </frame>
- </stac...
[truncated message content] |
|
From: Tom H. <to...@co...> - 2014-06-17 02:40:11
|
valgrind revision: 14049 VEX revision: 2878 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.13.10-200.fc20.x86_64 x86_64 Vendor version: Fedora release 16 (Verne) Nightly build on bristol ( x86_64, Fedora 16 ) Started at 2014-06-17 03:02:08 BST Ended at 2014-06-17 03:39: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 == 684 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) memcheck/tests/vbit-test/vbit-test (stderr) |
|
From: Siddharth N. <sn...@dr...> - 2014-06-17 02:27:54
|
Thanks Philippe. After some investigation, I believe what you mentioned is
happening exactly. My secondary maps in the shadow memory are sized at
2.5MB in the particular example we were discussing. This would result in
4MB block sizes being allocated by the VG_arena_malloc function. No matter
what the payload size, is it always going to alloc at 4MB chunks? Does the
pszB_to_bszB always return 4MB? I assume not, because the numbers from
profile-heap don't add up otherwise. Below is an example just before the
tool died:
--26681-- core : 1048576/ 1048576 max/curr mmap'd, 0/0 unsplit/split
sb unmmap'd, 50688/ 33904 max/curr, 6132/ 49980720
totalloc-blocks/bytes, 6131 searches
*--26681-- tool : 31516000256/31516000256 max/curr mmap'd, 0/0
unsplit/split sb unmmap'd, 19706049824/19706049824 max/curr,
20929/19706065264 totalloc-blocks/bytes, 28217271 searches*
--26681-- dinfo : 15945728/ 9846784 max/curr mmap'd, 3/2 unsplit/split
sb unmmap'd, 15245712/ 9109584 max/curr, 23407/ 30832000
totalloc-blocks/bytes, 23419 searches
--26681-- (null) : 0/ 0 max/curr mmap'd, 0/0 unsplit/split
sb unmmap'd, 0/ 0 max/curr, 0/ 0
totalloc-blocks/bytes, 0 searches
--26681-- demangle: 65536/ 0 max/curr mmap'd, 0/2 unsplit/split
sb unmmap'd, 176/ 0 max/curr, 168/ 4928
totalloc-blocks/bytes, 166 searches
--26681-- exectxt : 0/ 0 max/curr mmap'd, 0/0 unsplit/split
sb unmmap'd, 0/ 0 max/curr, 0/ 0
totalloc-blocks/bytes, 0 searches
--26681-- errors : 0/ 0 max/curr mmap'd, 0/0 unsplit/split
sb unmmap'd, 0/ 0 max/curr, 0/ 0
totalloc-blocks/bytes, 0 searches
--26681-- ttaux : 65536/ 65536 max/curr mmap'd, 0/0 unsplit/split
sb unmmap'd, 6160/ 6032 max/curr, 217/ 11488
totalloc-blocks/bytes, 216 searches
-------- Arena "core": 1048576/1048576 max/curr mmap'd, 0/0 unsplit/split
sb unmmap'd, 50688/33904 max/curr on_loan --------
32 in 1: stacks.rs.1
33,872 in 11: gdbsrv
*-------- Arena "tool": 31516000256/31516000256 max/curr mmap'd, 0/0
unsplit/split sb unmmap'd, 19706049824/19706049824 max/curr on_loan
--------*
16 in 1: sched_lock
64 in 1: cl.threads.nes.1
80 in 1: cl.init_funcarray.sys.3
80 in 1: cl.clo.nf.1
96 in 1: cl.dump.init_dumps.1
96 in 2: hashtable.Hc.1
112 in 1: options.efn.1
128 in 1: cl.dump.init_dumps.2
144 in 5: cl.events.group.1
160 in 2: commandline.sua.3
160 in 1: cl.events.geMapping.1
208 in 1: cl.init_funcarray.sys.4
208 in 2: commandline.sua.2
208 in 1: cl.threads.nt.1
256 in 1: initimg-linux.sce.5
400 in 7: cl.fn.non.2
448 in 7: cl.events.eventset.1
592 in 2: cl.clo.nc.1
640 in 13: cl.fn.nfn.2
3,840 in 8: cl.fn.non.1
4,000 in 1: cl.context.ifs.1
5,728 in 223: cl.fn.nfnnd.2
9,568 in 13: cl.fn.nfn.1
10,368 in 162: cl.funcinfo.gc.1
12,320 in 2: hashtable.Hc.2
17,840 in 223: cl.fn.nfnnd.1
20,304 in 1: cl.context.ict.1
28,000 in 1: cl.callstack.ics.1
29,824 in 466: cl.jumps.nj.1
35,504 in 1: cl.jumps.ijh.1
40,288 in 1: cl.fn.gfe.1
58,704 in 3,667: cl.bbcc.nr.1
67,504 in 1: cl.bb.ibh.1
80,080 in 1: cl.drwinit_thread.gc.1
80,080 in 1: cl.init_funcarray.sys.2
83,504 in 1: cl.bbcc.ibh.1
240,000 in 1: cl.init_funcarray.sys.1
259,200 in 162: cl.funccontext.gc.1
467,376 in 2,053: cl.bb.nb.1
475,072 in 571: cl.context.nc.1
521,712 in 3,752: cl.bbcc.nb.1
1,581,056 in 3: cl.sim.cs_ic.1
1,600,064 in 2: cl.costs.gc.1
2,621,440 in 1: cl.init_funcarray.sm.1
5,435,072 in 2,016: cl.funcinst.gc.1
*19,692,257,280 in 7,512: cl.copy_for_writing.sm.1 -----> Secondary Map
allocations*
As we can see, for the tool the "totalloc-blocks" are 20929, with its bytes
at about 18.3G.
20929 * 4MB is a very large number and much greater than even 29G which is
the reported size of the entire "tool" arena.
Looking at the details for the "tool" arena and counting the total number
of allocations, I see 20897 allocations, almost the same as 20929 shown at
the top. The allocations are dominated by my Secondary Map. I'm guessing
that fixing the size of the Secondary Maps to something that 'aligns' well
with 4MB (2.5MB does pretty terribly) will reduce the mismatch between
VMSpace and counted bytes allocated. Do you concur?
On 14 June 2014 05:10, Philippe Waroquiers <phi...@sk...>
wrote:
> On Fri, 2014-06-13 at 19:42 -0400, Siddharth Nilakantan wrote:
> > Philippe,
> >
> >
> > Thanks very much for that. I ran with what you said on my
> > single-threaded benchmark and got a line like the following just
> > before the tool died.
> >
> >
> > -------- Arena "tool": 31444697088/31444697088 max/curr mmap'd, 0/0
> > unsplit/split sb unmmap'd, 19661485344/19661485344 max/curr on_loan
> > --------
> >
> > <Here there is a breakdown of the various mallocs in the code>
> >
> >
> > This is a single-threaded benchmark, which creates just one "tool"
> > arena.
> > This indicates that the arena's size is close to 29.3GB while the
> > actual useable bytes (on_loan) are 18.3G. My calculation of malloc'ed
> > bytes also yields 18.3G so that part is correct.
> > Why is the arena size much larger? I currently do not free any memory,
> > so is the data segment growing in discrete and huge chunks on certain
> > malloc calls?
> Effectively, an arena is managed by mmap-ing big blocks of memory
> (e.g. 4Mb) which are split in smaller blocks according to what is
> VG_(malloc)-ed.
>
> Such a big difference between the mmap-ed and on_loan can be caused
> by 2 things:
> * allocating a lot of very small blocks (each malloc-ed block has
> an overhead. So, very small blocks proportionally causes a lot of
> overhead.
> * or by a 'unfriendly' pattern of malloc sizes.
> E.g. if the arena big block size is 4Mb, and you allocate a lot
> of 2Mb+1 "small blocks", that will cause a huge overhead.
>
> The details given by --profile-heap=yes should give some details
> about what is happening.
>
> Philippe
>
>
>
>
|
|
From: Rich C. <rc...@wi...> - 2014-06-17 02:02:24
|
valgrind revision: 14049
VEX revision: 2878
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-06-16 19:22:01 CDT
Ended at 2014-06-16 21:02:10 CDT
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
== 599 tests, 6 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)
memcheck/tests/vbit-test/vbit-test (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
== 599 tests, 89 stderr failures, 7 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/dw4 (stderr)
memcheck/tests/err_disable3 (stderr)
memcheck/tests/err_disable4 (stderr)
memcheck/tests/threadname (stderr)
memcheck/tests/threadname_xml (stderr)
memcheck/tests/varinfo1 (stderr)
memcheck/tests/varinfo2 (stderr)
memcheck/tests/varinfo3 (stderr)
memcheck/tests/varinfo4 (stdout)
memcheck/tests/varinfo4 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/varinfo6 (stdout)
memcheck/tests/varinfo6 (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
helgrind/tests/hg03_inherit (stderr)
helgrind/tests/hg04_race (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/rwlock_race (stderr)
helgrind/tests/tc01_simple_race (stderr)
helgrind/tests/tc05_simple_race (stderr)
helgrind/tests/tc06_two_races (stderr)
helgrind/tests/tc06_two_races_xml (stderr)
helgrind/tests/tc16_byterace (stderr)
helgrind/tests/tc20_verifywrap (stderr)
helgrind/tests/tc21_pthonce (stdout)
helgrind/tests/tc21_pthonce (stderr)
drd/tests/annotate_barrier (stderr)
drd/tests/annotate_barrier_xml (stderr)
drd/tests/annotate_hb_err (stderr)
drd/tests/annotate_hbefore (stderr)
drd/tests/annotate_ignore_read (stderr)
drd/tests/annotate_ignore_rw (stderr)
drd/tests/annotate_ignore_rw2 (stderr)
drd/tests/annotate_ignore_write (stderr)
drd/tests/annotate_ignore_write2 (stderr)
drd/tests/annotate_order_1 (stderr)
drd/tests/annotate_order_2 (stderr)
drd/tests/annotate_order_3 (stderr)
drd/tests/annotate_publish_hg (stderr)
drd/tests/annotate_rwlock (stderr)
drd/tests/annotate_rwlock_hg (stderr)
drd/tests/annotate_sem (stderr)
drd/tests/annotate_smart_pointer (stderr)
drd/tests/annotate_smart_pointer2 (stderr)
drd/tests/annotate_spinlock (stderr)
drd/tests/annotate_static (stderr)
drd/tests/annotate_trace_memory (stderr)
drd/tests/annotate_trace_memory_xml (stderr)
drd/tests/atomic_var (stderr)
drd/tests/boost_thread (stderr)
drd/tests/bug-235681 (stderr)
drd/tests/concurrent_close (stderr)
drd/tests/fp_race (stderr)
drd/tests/fp_race_xml (stderr)
drd/tests/free_is_write (stderr)
drd/tests/free_is_write2 (stderr)
drd/tests/hg03_inherit (stderr)
drd/tests/hg04_race (stderr)
drd/tests/hg05_race2 (stderr)
drd/tests/linuxthreads_det (stderr)
drd/tests/pth_cancel_locked (stderr)
drd/tests/pth_cleanup_handler (stderr)
drd/tests/pth_detached2 (stderr)
drd/tests/pth_mutex_reinit (stderr)
drd/tests/pth_once (stderr)
drd/tests/pth_process_shared_mutex (stderr)
drd/tests/pth_spinlock (stderr)
drd/tests/pth_uninitialized_cond (stderr)
drd/tests/recursive_mutex (stderr)
drd/tests/rwlock_race (stderr)
drd/tests/rwlock_test (stderr)
drd/tests/rwlock_type_checking (stderr)
drd/tests/sem_as_mutex (stderr)
drd/tests/sem_as_mutex2 (stderr)
drd/tests/sem_as_mutex3 (stderr)
drd/tests/sem_open (stderr)
drd/tests/sem_open2 (stderr)
drd/tests/sem_open3 (stderr)
drd/tests/sem_open_traced (stderr)
drd/tests/sem_wait (stderr)
drd/tests/tc01_simple_race (stderr)
drd/tests/tc16_byterace (stderr)
drd/tests/tc19_shadowmem (stderr)
drd/tests/tc24_nonzero_sem (stderr)
drd/tests/thread_name (stderr)
drd/tests/thread_name_xml (stderr)
exp-sgcheck/tests/bad_percentify (stdout)
exp-sgcheck/tests/bad_percentify (stderr)
exp-sgcheck/tests/globalerr (stderr)
exp-sgcheck/tests/hackedbz2 (stdout)
exp-sgcheck/tests/hackedbz2 (stderr)
exp-sgcheck/tests/hsg (stdout)
exp-sgcheck/tests/hsg (stderr)
exp-sgcheck/tests/preen_invars (stdout)
exp-sgcheck/tests/preen_invars (stderr)
exp-sgcheck/tests/stackerr (stderr)
=================================================
== Difference between 24 hours ago and now ==
=================================================
*** old.short Mon Jun 16 20:02:13 2014
--- new.short Mon Jun 16 21:02:10 2014
***************
*** 8,11 ****
! == 599 tests, 89 stderr failures, 7 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
! memcheck/tests/dw4 (stderr)
memcheck/tests/err_disable3 (stderr)
--- 8,10 ----
! == 599 tests, 6 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/err_disable3 (stderr)
***************
*** 14,106 ****
memcheck/tests/threadname_xml (stderr)
- memcheck/tests/varinfo1 (stderr)
- memcheck/tests/varinfo2 (stderr)
- memcheck/tests/varinfo3 (stderr)
- memcheck/tests/varinfo4 (stdout)
- memcheck/tests/varinfo4 (stderr)
- memcheck/tests/varinfo5 (stderr)
- memcheck/tests/varinfo6 (stdout)
- memcheck/tests/varinfo6 (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
- helgrind/tests/hg03_inherit (stderr)
- helgrind/tests/hg04_race (stderr)
- helgrind/tests/hg05_race2 (stderr)
- helgrind/tests/rwlock_race (stderr)
- helgrind/tests/tc01_simple_race (stderr)
- helgrind/tests/tc05_simple_race (stderr)
- helgrind/tests/tc06_two_races (stderr)
- helgrind/tests/tc06_two_races_xml (stderr)
- helgrind/tests/tc16_byterace (stderr)
- helgrind/tests/tc20_verifywrap (stderr)
- helgrind/tests/tc21_pthonce (stdout)
- helgrind/tests/tc21_pthonce (stderr)
- drd/tests/annotate_barrier (stderr)
- drd/tests/annotate_barrier_xml (stderr)
- drd/tests/annotate_hb_err (stderr)
- drd/tests/annotate_hbefore (stderr)
- drd/tests/annotate_ignore_read (stderr)
- drd/tests/annotate_ignore_rw (stderr)
- drd/tests/annotate_ignore_rw2 (stderr)
- drd/tests/annotate_ignore_write (stderr)
- drd/tests/annotate_ignore_write2 (stderr)
- drd/tests/annotate_order_1 (stderr)
- drd/tests/annotate_order_2 (stderr)
- drd/tests/annotate_order_3 (stderr)
- drd/tests/annotate_publish_hg (stderr)
- drd/tests/annotate_rwlock (stderr)
- drd/tests/annotate_rwlock_hg (stderr)
- drd/tests/annotate_sem (stderr)
- drd/tests/annotate_smart_pointer (stderr)
- drd/tests/annotate_smart_pointer2 (stderr)
- drd/tests/annotate_spinlock (stderr)
- drd/tests/annotate_static (stderr)
- drd/tests/annotate_trace_memory (stderr)
- drd/tests/annotate_trace_memory_xml (stderr)
- drd/tests/atomic_var (stderr)
- drd/tests/boost_thread (stderr)
- drd/tests/bug-235681 (stderr)
- drd/tests/concurrent_close (stderr)
- drd/tests/fp_race (stderr)
- drd/tests/fp_race_xml (stderr)
- drd/tests/free_is_write (stderr)
- drd/tests/free_is_write2 (stderr)
- drd/tests/hg03_inherit (stderr)
- drd/tests/hg04_race (stderr)
- drd/tests/hg05_race2 (stderr)
- drd/tests/linuxthreads_det (stderr)
- drd/tests/pth_cancel_locked (stderr)
- drd/tests/pth_cleanup_handler (stderr)
- drd/tests/pth_detached2 (stderr)
- drd/tests/pth_mutex_reinit (stderr)
- drd/tests/pth_once (stderr)
- drd/tests/pth_process_shared_mutex (stderr)
- drd/tests/pth_spinlock (stderr)
- drd/tests/pth_uninitialized_cond (stderr)
- drd/tests/recursive_mutex (stderr)
- drd/tests/rwlock_race (stderr)
- drd/tests/rwlock_test (stderr)
- drd/tests/rwlock_type_checking (stderr)
- drd/tests/sem_as_mutex (stderr)
- drd/tests/sem_as_mutex2 (stderr)
- drd/tests/sem_as_mutex3 (stderr)
- drd/tests/sem_open (stderr)
- drd/tests/sem_open2 (stderr)
- drd/tests/sem_open3 (stderr)
- drd/tests/sem_open_traced (stderr)
- drd/tests/sem_wait (stderr)
- drd/tests/tc01_simple_race (stderr)
- drd/tests/tc16_byterace (stderr)
- drd/tests/tc19_shadowmem (stderr)
- drd/tests/tc24_nonzero_sem (stderr)
- drd/tests/thread_name (stderr)
- drd/tests/thread_name_xml (stderr)
- exp-sgcheck/tests/bad_percentify (stdout)
- exp-sgcheck/tests/bad_percentify (stderr)
- exp-sgcheck/tests/globalerr (stderr)
- exp-sgcheck/tests/hackedbz2 (stdout)
exp-sgcheck/tests/hackedbz2 (stderr)
- exp-sgcheck/tests/hsg (stdout)
- exp-sgcheck/tests/hsg (stderr)
- exp-sgcheck/tests/preen_invars (stdout)
- exp-sgcheck/tests/preen_invars (stderr)
- exp-sgcheck/tests/stackerr (stderr)
--- 13,16 ----
=================================================
./valgrind-new/exp-sgcheck/tests/hackedbz2.stderr.diff-glibc28-amd64
=================================================
--- hackedbz2.stderr.exp-glibc28-amd64 2014-06-16 20:03:03.215695773 -0500
+++ hackedbz2.stderr.out 2014-06-16 21:00:59.000016445 -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-06-16 20:02:56.810621471 -0500
+++ err_disable3.stderr.out 2014-06-16 20:21:56.533842777 -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-06-16 20:02:51.428559037 -0500
+++ err_disable4.stderr.out 2014-06-16 20:22:00.927893750 -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-06-16 20:02:57.705631854 -0500
+++ threadname.stderr.out 2014-06-16 20:28:08.997163520 -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-06-16 20:02:51.440559176 -0500
+++ threadname_xml.stderr.out 2014-06-16 20:28:11.131188276 -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-new/memcheck/tests/vbit-test/vbit-test.stderr.diff
=================================================
--- vbit-test.stderr.exp 2014-06-16 20:02:52.888575974 -0500
+++ vbit-test.stderr.out 2014-06-16 20:30:06.281524072 -0500
@@ -0,0 +1 @@
+unknown opcode 5824
=================================================
./valgrind-old/drd/tests/annotate_barrier.stderr.diff
=================================================
--- annotate_barrier.stderr.exp 2014-06-16 19:23:34.038212242 -0500
+++ annotate_barrier.stderr.out 2014-06-16 19:58:18.926397839 -0500
@@ -1,47 +1,23 @@
-The annotation macro ANNOTATE_BARRIER_INIT has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_init (annotate_barrier.c:?)
- by 0x........: barriers_and_races (annotate_barrier.c:?)
- by 0x........: main (annotate_barrier.c:?)
-
-Thread 2:
-The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-Thread 3:
-The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-Thread 2:
-Conflicting store by thread 2 at 0x........ size 4
- at 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
- by 0x........: (within libpthread-?.?.so)
-Address 0x........ is at offset 0 from 0x......... Allocation context:
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: barriers_and_races (annotate_barrier.c:?)
- by 0x........: main (annotate_barrier.c:?)
-
-The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_wait (annotate_barrier.c:?)
- by 0x........: threadfunc (annotate_barrier.c:?)
- by 0x........: vgDrd_thread_wrapper (drd_pthread_intercepts.c:?)
-
-Thread 1:
-The annotation macro ANNOTATE_BARRIER_DESTROY has not yet been implemented in <valgrind/drd.h>
- at 0x........: barrier_destroy (annotate_barrier.c:?)
- by 0x........: barriers_and_races (annotate_barrier.c:?)
- by 0x........: main (annotate_barrier.c:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 11 errors from 7 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_barrier_xml.stderr.diff
=================================================
--- annotate_barrier_xml.stderr.exp 2014-06-16 19:23:34.235214527 -0500
+++ annotate_barrier_xml.stderr.out 2014-06-16 19:58:19.119400078 -0500
@@ -26,302 +26,26 @@
</argv>
</args>
-<status>
- <state>RUNNING</state>
- <time>...</time>
-</status>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <kind>UnimpDrdClReq</kind>
- <what>The annotation macro ANNOTATE_BARRIER_INIT has not yet been implemented in <valgrind/drd.h></what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barrier_init</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barriers_and_races</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>main</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- </stack>
-</error>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <kind>UnimpDrdClReq</kind>
- <what>The annotation macro ANNOTATE_BARRIER_WAIT_BEFORE has not yet been implemented in <valgrind/drd.h></what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barrier_wait</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>threadfunc</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>vgDrd_thread_wrapper</fn>
- <dir>...</dir>
- <file>drd_pthread_intercepts.c</file>
- <line>...</line>
- </frame>
- </stack>
-</error>
-
-<error>
- <unique>0x........</unique>
- <tid>...</tid>
- <kind>UnimpDrdClReq</kind>
- <what>The annotation macro ANNOTATE_BARRIER_WAIT_AFTER has not yet been implemented in <valgrind/drd.h></what>
- <stack>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>barrier_wait</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
- <ip>0x........</ip>
- <obj>...</obj>
- <fn>threadfunc</fn>
- <dir>...</dir>
- <file>annotate_barrier.c</file>
- <line>...</line>
- </frame>
- <frame>
<truncated beyond 100 lines>
=================================================
./valgrind-old/drd/tests/annotate_hb_err.stderr.diff
=================================================
--- annotate_hb_err.stderr.exp 2014-06-16 19:23:34.218214330 -0500
+++ annotate_hb_err.stderr.out 2014-06-16 19:58:19.306402247 -0500
@@ -1,25 +1,23 @@
-wrong type of synchronization object
- at 0x........: U_AnnotateHappensBefore (unified_annotations.h:?)
- by 0x........: main (annotate_hb_err.c:?)
-mutex 0x........ was first observed at:
- at 0x........: pthread_mutex_init (drd_pthread_intercepts.c:?)
- by 0x........: main (annotate_hb_err.c:?)
-
-wrong type of synchronization object
- at 0x........: U_AnnotateHappensBefore (unified_annotations.h:?)
- by 0x........: main (annotate_hb_err.c:?)
-cond 0x........ was first observed at:
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (annotate_hb_err.c:?)
-
-wrong type of synchronization object
- at 0x........: pthread_cond_init (drd_pthread_intercepts.c:?)
- by 0x........: main (annotate_hb_err.c:?)
-order annotation 0x........ was first observed at:
- at 0x........: U_AnnotateHappensAfter (unified_annotations.h:?)
- by 0x........: main (annotate_hb_err.c:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_hbefore.stderr.diff
=================================================
--- annotate_hbefore.stderr.exp 2014-06-16 19:23:34.136213378 -0500
+++ annotate_hbefore.stderr.out 2014-06-16 19:58:21.371426202 -0500
@@ -1,3 +1,23 @@
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_ignore_read.stderr.diff
=================================================
--- annotate_ignore_read.stderr.exp 2014-06-16 19:23:34.225214411 -0500
+++ annotate_ignore_read.stderr.out 2014-06-16 19:58:21.577428592 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test69: negative
- GLOB=30
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_ignore_rw.stderr.diff
=================================================
--- annotate_ignore_rw.stderr.exp 2014-06-16 19:23:34.096212914 -0500
+++ annotate_ignore_rw.stderr.out 2014-06-16 19:58:21.722430274 -0500
@@ -1,9 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_rw.c:12
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_ignore_rw2.stderr.diff
=================================================
--- annotate_ignore_rw2.stderr.exp 2014-06-16 19:23:34.125213251 -0500
+++ annotate_ignore_rw2.stderr.out 2014-06-16 19:58:21.857431840 -0500
@@ -1,19 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_b"
-declared at annotate_ignore_rw.c:11
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_rw.c:10
-
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_rw.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_rw.c:12
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_ignore_write.stderr.diff
=================================================
--- annotate_ignore_write.stderr.exp 2014-06-16 19:23:34.247214666 -0500
+++ annotate_ignore_write.stderr.out 2014-06-16 19:58:22.020433731 -0500
@@ -1,19 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_b"
-declared at annotate_ignore_write.c:11
-
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_write.c:12
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_write.c:10
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_ignore_write2.stderr.diff
=================================================
--- annotate_ignore_write2.stderr.exp 2014-06-16 19:23:34.033212184 -0500
+++ annotate_ignore_write2.stderr.out 2014-06-16 19:58:22.163435390 -0500
@@ -1,24 +1,23 @@
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_b"
-declared at annotate_ignore_write.c:11
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_write.c:10
-
-Conflicting load by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_c"
-declared at annotate_ignore_write.c:12
-
-Conflicting store by thread 1 at 0x........ size 1
- at 0x........: main (annotate_ignore_write.c:?)
-Location 0x........ is 0 bytes inside global var "s_a"
-declared at annotate_ignore_write.c:10
-Finished.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_order_1.stderr.diff
=================================================
--- annotate_order_1.stderr.exp 2014-06-16 19:23:34.129213297 -0500
+++ annotate_order_1.stderr.out 2014-06-16 19:58:22.340437443 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test03: negative
- GLOB=2
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_order_2.stderr.diff
=================================================
--- annotate_order_2.stderr.exp 2014-06-16 19:23:34.045212323 -0500
+++ annotate_order_2.stderr.out 2014-06-16 19:58:22.500439299 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test30: negative
- GLOB=47
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_order_3.stderr.diff
=================================================
--- annotate_order_3.stderr.exp 2014-06-16 19:23:34.232214492 -0500
+++ annotate_order_3.stderr.out 2014-06-16 19:58:22.660441155 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test31: negative
- GLOB=48
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_publish_hg.stderr.diff
=================================================
--- annotate_publish_hg.stderr.exp 2014-06-16 19:23:33.995211743 -0500
+++ annotate_publish_hg.stderr.out 2014-06-16 19:58:22.806442849 -0500
@@ -1,7 +1,23 @@
-The annotation macro ANNOTATE_PUBLISH_MEMORY_RANGE has not yet been implemented in <valgrind/helgrind.h>
- at 0x........: main (annotate_publish_hg.c:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_rwlock.stderr.diff
=================================================
--- annotate_rwlock.stderr.exp 2014-06-16 19:23:34.000211801 -0500
+++ annotate_rwlock.stderr.out 2014-06-16 19:58:22.970444751 -0500
@@ -1,4 +1,23 @@
-Finished.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_rwlock_hg.stderr.diff
=================================================
--- annotate_rwlock_hg.stderr.exp 2014-06-16 19:23:34.157213622 -0500
+++ annotate_rwlock_hg.stderr.out 2014-06-16 19:58:23.033445482 -0500
@@ -1 +0,0 @@
-Total error count is below threshold.
=================================================
./valgrind-old/drd/tests/annotate_sem.stderr.diff
=================================================
--- annotate_sem.stderr.exp 2014-06-16 19:23:34.213214272 -0500
+++ annotate_sem.stderr.out 2014-06-16 19:58:23.180447187 -0500
@@ -1,4 +1,23 @@
-Finished.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_smart_pointer.stderr.diff
=================================================
--- annotate_smart_pointer.stderr.exp 2014-06-16 19:23:34.057212462 -0500
+++ annotate_smart_pointer.stderr.out 2014-06-16 19:58:23.324448858 -0500
@@ -1,4 +1,23 @@
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_smart_pointer2.stderr.diff
=================================================
--- annotate_smart_pointer2.stderr.exp 2014-06-16 19:23:34.002211824 -0500
+++ annotate_smart_pointer2.stderr.out 2014-06-16 19:58:23.473450586 -0500
@@ -1,13 +1,23 @@
-Conflicting store by thread x at 0x........ size 4
- at 0x........: counter::~counter() (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::set(counter*, AtomicInt32*) (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::operator=(counter*) (annotate_smart_pointer.cpp:?)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Address 0x........ is at offset ... from 0x......... Allocation context:
- at 0x........: ...operator new... (vg_replace_malloc.c:...)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_smart_pointer2.stderr.diff-darwin
=================================================
--- annotate_smart_pointer2.stderr.exp-darwin 2014-06-16 19:23:34.077212694 -0500
+++ annotate_smart_pointer2.stderr.out 2014-06-16 19:58:23.473450586 -0500
@@ -1,14 +1,23 @@
-Conflicting store by thread x at 0x........ size 4
- at 0x........: counter::~counter() (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::set(counter*, AtomicInt32*) (annotate_smart_pointer.cpp:?)
- by 0x........: smart_ptr<counter>::operator=(counter*) (annotate_smart_pointer.cpp:?)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Address 0x........ is at offset ... from 0x......... Allocation context:
- at 0x........: malloc (vg_replace_malloc.c:...)
- by 0x........: operator new(unsigned long) (in /usr/lib/libstdc++.6.0.9.dylib)
- by 0x........: main (annotate_smart_pointer.cpp:?)
-Done.
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
=================================================
./valgrind-old/drd/tests/annotate_spinlock.stderr.diff
=================================================
--- annotate_spinlock.stderr.exp 2014-06-16 19:23:34.026212102 -0500
+++ annotate_spinlock.stderr.out 2014-06-16 19:58:23.642452547 -0500
@@ -1,6 +1,23 @@
-FLAGS [phb=1, fm=0]
-test27: negative
- GLOB=4
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_static.stderr.diff
=================================================
--- annotate_static.stderr.exp 2014-06-16 19:23:34.160213657 -0500
+++ annotate_static.stderr.out 2014-06-16 19:58:23.883455343 -0500
@@ -1,4 +1,23 @@
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_trace_memory.stderr.diff-32bit
=================================================
--- annotate_trace_memory.stderr.exp-32bit 2014-06-16 19:23:34.136213378 -0500
+++ annotate_trace_memory.stderr.out 2014-06-16 19:58:24.031457060 -0500
@@ -1,52 +1,23 @@
-float
-store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-double
-store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 8 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint8_t
-store 0x........ size 1 val 5/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 1 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 1 val 11/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint16_t
-store 0x........ size 2 val 7/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 2 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 2 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint32_t
-store 0x........ size 4 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint64_t
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 305419905/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_trace_memory.stderr.diff-64bit
=================================================
--- annotate_trace_memory.stderr.exp-64bit 2014-06-16 19:23:34.174213819 -0500
+++ annotate_trace_memory.stderr.out 2014-06-16 19:58:24.031457060 -0500
@@ -1,46 +1,23 @@
-float
-store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-double
-store 0x........ size 8 val 4613937818241073152/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 8 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 8 val 4619567317775286272/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint8_t
-store 0x........ size 1 val 5/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 1 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 1 val 11/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint16_t
-store 0x........ size 2 val 7/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 2 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 2 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint32_t
-store 0x........ size 4 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint64_t
-store 0x........ size 8 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 8 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 8 val 305419905/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgrind/nightly/valgrind-old/drd/drd-amd64-linux)
+
+sched status:
+ running_tid=0
+
+
+Note: see also the FAQ in the source distribution.
+It contains workarounds to several common problems.
+In particular, if Valgrind aborted or crashed after
+identifying problems in your program, there's a good chance
+that fixing those problems will prevent Valgrind aborting or
+crashing, especially if it happened in m_mallocfree.c.
+
+If that doesn't help, please report this bug to: www.valgrind.org
+
+In the bug report, send all the above text, the valgrind
+version, and what OS and version you are using. Thanks.
+
=================================================
./valgrind-old/drd/tests/annotate_trace_memory.stderr.diff-mips32
=================================================
--- annotate_trace_memory.stderr.exp-mips32 2014-06-16 19:23:34.166213726 -0500
+++ annotate_trace_memory.stderr.out 2014-06-16 19:58:24.031457060 -0500
@@ -1,58 +1,23 @@
-float
-store 0x........ size 4 val 1065353216/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1077936128/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-double
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1074266112/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 1075576832/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint8_t
-store 0x........ size 1 val 5/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 1 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 1 val 11/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint16_t
-store 0x........ size 2 val 7/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 2 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 2 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint32_t
-store 0x........ size 4 val 8/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-uint64_t
-store 0x........ size 4 val 9/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-load 0x........ size 4 (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 305419905/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-store 0x........ size 4 val 0/0x........ (thread x / vc ...)
- at 0x........: main (annotate_trace_memory.c:?)
-Done.
-ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
+valgrind: m_debuginfo/readdwarf3.c:4374 (new_dwarf3_reader_wrk): Assertion 'inlparser.filenameTable' failed.
+
+host stacktrace:
+ at 0x........: ??? (in /usr/local/src/valgri...
[truncated message content] |