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-16 21:49:51
|
Author: philippe
Date: Mon Jun 16 21:49:42 2014
New Revision: 14049
Log:
optimisation : avoid double reading of a DIE when the DIE will be parsed
by a DIE parser
Instead of pre-reading the DIE, first let the parser(s) possibly
parse the DIE. Read (to skip) the DIE data if no parser has parsed it.
OTherwise, just jump to the end of the DIE as established by the parser
that has read the DIE.
This slightly improves the reading of inlined info.
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 Mon Jun 16 21:49:42 2014
@@ -2199,6 +2199,7 @@
/* The file name table. Is a mapping from integer index to the
(permanent) copy of the string in DebugInfo's .strchunks. */
XArray* /* of UChar* */ filenameTable;
+ UWord sibling; // sibling of the last read DIE (if it has a sibling).
}
D3InlParser;
@@ -2302,6 +2303,9 @@
if (attr == DW_AT_stmt_list && cts.szB > 0) {
read_filename_table( parser->filenameTable, cc, cts.u.val, td3 );
}
+ if (attr == DW_AT_sibling && cts.szB > 0) {
+ parser->sibling = cts.u.val;
+ }
}
if (level == 0)
setup_cu_svma (cc, have_lo, ip_lo, td3);
@@ -2358,6 +2362,9 @@
rangeoff = cts.u.val;
have_range = True;
}
+ if (attr == DW_AT_sibling && cts.szB > 0) {
+ parser->sibling = cts.u.val;
+ }
}
if (have_lo && have_hi1 && hiIsRelative)
ip_hi1 += ip_lo;
@@ -3704,7 +3711,6 @@
{
g_abbv *abbv;
ULong atag, abbv_code;
- UInt nf_i;
UWord posn;
UInt has_children;
UWord start_die_c_offset;
@@ -3735,46 +3741,11 @@
/* We're set up to look at the fields of this DIE. Hand it off to
any parser(s) that want to see it. Since they will in general
advance the DIE cursor, remember the current settings so that we
- can then back up and do one final pass over the DIE, to print out
- its contents. */
+ can then back up. . */
start_die_c_offset = get_position_of_Cursor( c );
-
- /* "pre-read" the DIE (while doing nothing with the data)
- for 3 reasons:
- 1. it td3, trace the DIE data.
- 2. determine if this DIE has a sibling (used for
- optimising when only reading the inline info).
- 3. determine the end of the DIE (after_die_c_offset).
-
- The parsers below will re-read the DIEs if they are interested
- in the atag. The var/type parsers re-read many DIEs. The
- inline parser re-reads a smaller subset.
- We could possibly avoid this double reading by having each
- parser optionally parse the DIE and (if needed) skip
- the DIE data if it was not read by any parser. */
- nf_i = 0;
- while (True) {
- FormContents cts;
- ULong at_name = abbv->nf[nf_i].at_name;
- 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 */
- get_Form_contents( &cts, cc, c, td3, (DW_FORM)at_form );
- /* Except that we remember if this DIE has a sibling. */
- if (UNLIKELY(at_name == DW_AT_sibling && cts.szB > 0)) {
- sibling = cts.u.val;
- }
- TRACE_D3("\t");
- TRACE_D3("\n");
- }
- after_die_c_offset = get_position_of_Cursor( c );
+ after_die_c_offset = 0; // set to c position if a parser has read the DIE.
if (VG_(clo_read_var_info)) {
- set_position_of_Cursor( c, start_die_c_offset );
-
parse_type_DIE( tyents,
typarser,
(DW_TAG)atag,
@@ -3784,8 +3755,10 @@
abbv, /* abbrev */
cc,
td3 );
-
- set_position_of_Cursor( c, start_die_c_offset );
+ if (get_position_of_Cursor( c ) != start_die_c_offset) {
+ after_die_c_offset = get_position_of_Cursor( c );
+ set_position_of_Cursor( c, start_die_c_offset );
+ }
parse_var_DIE( rangestree,
tempvars,
@@ -3798,14 +3771,18 @@
abbv, /* abbrev */
cc,
td3 );
+ if (get_position_of_Cursor( c ) != start_die_c_offset) {
+ after_die_c_offset = get_position_of_Cursor( c );
+ set_position_of_Cursor( c, start_die_c_offset );
+ }
parse_children = True;
- // type and var parsers do not have logic to skip childrens.
+ // type and var parsers do not have logic to skip childrens and establish
+ // the value of sibling.
}
if (VG_(clo_read_inline_info)) {
- set_position_of_Cursor( c, start_die_c_offset );
-
+ inlparser->sibling = 0;
parse_children =
parse_inl_DIE( inlparser,
(DW_TAG)atag,
@@ -3816,9 +3793,43 @@
cc,
td3 )
|| parse_children;
+ if (get_position_of_Cursor( c ) != start_die_c_offset) {
+ after_die_c_offset = get_position_of_Cursor( c );
+ // Last parser, no need to reset the cursor to start_die_c_offset.
+ }
+ if (sibling == 0)
+ sibling = inlparser->sibling;
+ vg_assert (inlparser->sibling == 0 || inlparser->sibling == sibling);
}
- set_position_of_Cursor( c, after_die_c_offset );
+ if (after_die_c_offset > 0) {
+ // DIE was read by a parser above, so we know where the DIE ends.
+ set_position_of_Cursor( c, after_die_c_offset );
+ } else {
+ /* No parser has parsed this DIE. So, we need to read the DIE
+ to skip its data, in order to read the next DIE.
+ At the same time, establish sibling value if the DIE has one. */
+ UInt nf_i;
+
+ nf_i = 0;
+ while (True) {
+ FormContents cts;
+ ULong at_name = abbv->nf[nf_i].at_name;
+ 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. */
+ if (UNLIKELY(at_name == DW_AT_sibling && cts.szB > 0)) {
+ sibling = cts.u.val;
+ }
+ TRACE_D3("\t");
+ TRACE_D3("\n");
+ }
+ }
/* --- Now recurse into its children, if any
and the parsing of the children is requested by a parser --- */
|
|
From: <sv...@va...> - 2014-06-16 21:26:32
|
Author: philippe
Date: Mon Jun 16 21:26:24 2014
New Revision: 14048
Log:
Refine NEWS entry for helgrind Ada tasks intercepts
Modified:
trunk/NEWS
Modified: trunk/NEWS
==============================================================================
--- trunk/NEWS (original)
+++ trunk/NEWS Mon Jun 16 21:26:24 2014
@@ -19,7 +19,9 @@
the list of locks, their location, and their status.
- Helgrind now understands the Ada task termination rules
and creates a 'H-B relationship' between a terminated task and
- its master. This only works with gnatpro >= 7.3.0w-20140611
+ its master. This avoids some false positive and avoids big
+ memory usage when a lot of Ada tasks are created and terminated.
+ The interceptions are only activated with gnatpro >= 7.3.0w-20140611
or gcc >= ????? (TBD: check when changes pushed to FSF gcc).
* Callgrind:
|
|
From: <sv...@va...> - 2014-06-16 21:25:41
|
Author: philippe
Date: Mon Jun 16 21:25:31 2014
New Revision: 14047
Log:
Use a string literal format to avoid a gcc warning (-Wformat-security)
Modified:
trunk/coregrind/m_debuginfo/debuginfo.c
Modified: trunk/coregrind/m_debuginfo/debuginfo.c
==============================================================================
--- trunk/coregrind/m_debuginfo/debuginfo.c (original)
+++ trunk/coregrind/m_debuginfo/debuginfo.c Mon Jun 16 21:25:31 2014
@@ -2112,7 +2112,7 @@
: NULL;
vg_assert (cur_inl);
// The filename and lineno for the inlined fn caller is in cur_inl.
- VG_(snprintf) (buf_srcloc, BUF_LEN, cur_inl->filename);
+ VG_(snprintf) (buf_srcloc, BUF_LEN, "%s", cur_inl->filename);
lineno = cur_inl->lineno;
know_dirinfo = False; //INLINED TBD
|
|
From: <sv...@va...> - 2014-06-16 20:00:27
|
Author: philippe
Date: Mon Jun 16 20:00:14 2014
New Revision: 14046
Log:
Add helgrind intercepts to have helgrind understanding Ada tasks terination rules
A recent gnatpro version is needed for this to work.
Thanks to these intercepts, some false positive errors are avoided,
and helgrind properly recuperates some internal memory associated
to the terminated task.
Modified:
trunk/NEWS
trunk/helgrind/helgrind.h
trunk/helgrind/hg_intercepts.c
trunk/helgrind/hg_main.c
Modified: trunk/NEWS
==============================================================================
--- trunk/NEWS (original)
+++ trunk/NEWS Mon Jun 16 20:00:14 2014
@@ -17,6 +17,10 @@
* Helgrind:
- Helgrind GDB server monitor command 'info locks' giving
the list of locks, their location, and their status.
+ - Helgrind now understands the Ada task termination rules
+ and creates a 'H-B relationship' between a terminated task and
+ its master. This only works with gnatpro >= 7.3.0w-20140611
+ or gcc >= ????? (TBD: check when changes pushed to FSF gcc).
* Callgrind:
- callgrind_control now supports the --vgdb-prefix argument,
Modified: trunk/helgrind/helgrind.h
==============================================================================
--- trunk/helgrind/helgrind.h (original)
+++ trunk/helgrind/helgrind.h Mon Jun 16 20:00:14 2014
@@ -116,8 +116,10 @@
_VG_USERREQ__HG_ARANGE_MAKE_TRACKED, /* Addr a, ulong len */
_VG_USERREQ__HG_PTHREAD_BARRIER_RESIZE_PRE, /* pth_bar_t*, ulong */
_VG_USERREQ__HG_CLEAN_MEMORY_HEAPBLOCK, /* Addr start_of_block */
- _VG_USERREQ__HG_PTHREAD_COND_INIT_POST /* pth_cond_t*, pth_cond_attr_t*/
-
+ _VG_USERREQ__HG_PTHREAD_COND_INIT_POST, /* pth_cond_t*, pth_cond_attr_t*/
+ _VG_USERREQ__HG_GNAT_MASTER_HOOK, /* void*d,void*m,Word ml */
+ _VG_USERREQ__HG_GNAT_MASTER_COMPLETED_HOOK /* void*s,Word ml */
+
} Vg_TCheckClientRequest;
Modified: trunk/helgrind/hg_intercepts.c
==============================================================================
--- trunk/helgrind/hg_intercepts.c (original)
+++ trunk/helgrind/hg_intercepts.c Mon Jun 16 20:00:14 2014
@@ -60,6 +60,7 @@
#define TRACE_PTH_FNS 0
#define TRACE_QT4_FNS 0
+#define TRACE_GNAT_FNS 0
/*----------------------------------------------------------------*/
@@ -403,6 +404,80 @@
done. No way the joiner can return before the thread is gone.
*/
+//-----------------------------------------------------------
+// Ada gcc gnat runtime:
+// The gnat gcc Ada runtime does not use pthread_join. Instead, it uses
+// a combination of other pthread primitives to ensure a child thread
+// is gone. This combination is somewhat functionally equivalent to a
+// pthread_join.
+// We wrap two hook procedures called by the gnat gcc Ada runtime
+// that allows helgrind to understand the semantic of Ada task dependencies
+// and termination.
+
+// System.Tasking.Debug.Master_Hook is called by a task Dependent to
+// indicate that its master is identified by master+master_level.
+void I_WRAP_SONAME_FNNAME_ZU
+ (Za,
+ system__tasking__debug__master_hook)
+ (void *dependent, void *master, int master_level);
+void I_WRAP_SONAME_FNNAME_ZU
+ (Za,
+ system__tasking__debug__master_hook)
+ (void *dependent, void *master, int master_level)
+{
+ OrigFn fn;
+ VALGRIND_GET_ORIG_FN(fn);
+ if (TRACE_GNAT_FNS) {
+ fprintf(stderr, "<< GNAT master_hook wrapper "
+ "dependent %p master %p master_level %d\n",
+ dependent, master, master_level); fflush(stderr);
+ }
+
+ // We call the wrapped function, even if it is a null body.
+ CALL_FN_v_WWW(fn, dependent, master, master_level);
+
+ DO_CREQ_v_WWW(_VG_USERREQ__HG_GNAT_MASTER_HOOK,
+ void*,dependent, void*,master,
+ Word, (Word)master_level);
+
+ if (TRACE_GNAT_FNS) {
+ fprintf(stderr, " :: GNAT master_hook >>\n");
+ }
+}
+
+// System.Tasking.Debug.Master_Completed_Hook is called by a task to
+// indicate that it has completed a master.
+// This indicates that all its Dependent tasks (that identified themselves
+// with the Master_Hook call) are terminated. Helgrind can consider
+// at this point that the equivalent of a 'pthread_join' has been done
+// between self_id and all dependent tasks at master_level.
+void I_WRAP_SONAME_FNNAME_ZU
+ (Za,
+ system__tasking__debug__master_completed_hook)
+ (void *self_id, int master_level);
+void I_WRAP_SONAME_FNNAME_ZU
+ (Za,
+ system__tasking__debug__master_completed_hook)
+ (void *self_id, int master_level)
+{
+ OrigFn fn;
+ VALGRIND_GET_ORIG_FN(fn);
+ if (TRACE_GNAT_FNS) {
+ fprintf(stderr, "<< GNAT master_completed_hook wrapper "
+ "self_id %p master_level %d\n",
+ self_id, master_level); fflush(stderr);
+ }
+
+ // We call the wrapped function, even if it is a null body.
+ CALL_FN_v_WW(fn, self_id, master_level);
+
+ DO_CREQ_v_WW(_VG_USERREQ__HG_GNAT_MASTER_COMPLETED_HOOK,
+ void*,self_id, Word,(Word)master_level);
+
+ if (TRACE_GNAT_FNS) {
+ fprintf(stderr, " :: GNAT master_completed_hook >>\n");
+ }
+}
/*----------------------------------------------------------------*/
/*--- pthread_mutex_t functions ---*/
Modified: trunk/helgrind/hg_main.c
==============================================================================
--- trunk/helgrind/hg_main.c (original)
+++ trunk/helgrind/hg_main.c Mon Jun 16 20:00:14 2014
@@ -1670,6 +1670,36 @@
}
}
+/* generate a dependence from the hbthr_q quitter to the hbthr_s stayer. */
+static
+void generate_quitter_stayer_dependence (Thr* hbthr_q, Thr* hbthr_s)
+{
+ SO* so;
+ /* Allocate a temporary synchronisation object and use it to send
+ an imaginary message from the quitter to the stayer, the purpose
+ being to generate a dependence from the quitter to the
+ stayer. */
+ so = libhb_so_alloc();
+ tl_assert(so);
+ /* Send last arg of _so_send as False, since the sending thread
+ doesn't actually exist any more, so we don't want _so_send to
+ try taking stack snapshots of it. */
+ libhb_so_send(hbthr_q, so, True/*strong_send*//*?!? wrt comment above*/);
+ libhb_so_recv(hbthr_s, so, True/*strong_recv*/);
+ libhb_so_dealloc(so);
+
+ /* Tell libhb that the quitter has been reaped. Note that we might
+ have to be cleverer about this, to exclude 2nd and subsequent
+ notifications for the same hbthr_q, in the case where the app is
+ buggy (calls pthread_join twice or more on the same thread) AND
+ where libpthread is also buggy and doesn't return ESRCH on
+ subsequent calls. (If libpthread isn't thusly buggy, then the
+ wrapper for pthread_join in hg_intercepts.c will stop us getting
+ notified here multiple times for the same joinee.) See also
+ comments in helgrind/tests/jointwice.c. */
+ libhb_joinedwith_done(hbthr_q);
+}
+
static
void evh__HG_PTHREAD_JOIN_POST ( ThreadId stay_tid, Thread* quit_thr )
@@ -1678,7 +1708,6 @@
Thread* thr_q;
Thr* hbthr_s;
Thr* hbthr_q;
- SO* so;
if (SHOW_EVENTS >= 1)
VG_(printf)("evh__post_thread_join(stayer=%d, quitter=%p)\n",
@@ -1698,29 +1727,7 @@
tl_assert( libhb_get_Thr_hgthread(hbthr_s) == thr_s );
tl_assert( libhb_get_Thr_hgthread(hbthr_q) == thr_q );
- /* Allocate a temporary synchronisation object and use it to send
- an imaginary message from the quitter to the stayer, the purpose
- being to generate a dependence from the quitter to the
- stayer. */
- so = libhb_so_alloc();
- tl_assert(so);
- /* Send last arg of _so_send as False, since the sending thread
- doesn't actually exist any more, so we don't want _so_send to
- try taking stack snapshots of it. */
- libhb_so_send(hbthr_q, so, True/*strong_send*//*?!? wrt comment above*/);
- libhb_so_recv(hbthr_s, so, True/*strong_recv*/);
- libhb_so_dealloc(so);
-
- /* Tell libhb that the quitter has been reaped. Note that we might
- have to be cleverer about this, to exclude 2nd and subsequent
- notifications for the same hbthr_q, in the case where the app is
- buggy (calls pthread_join twice or more on the same thread) AND
- where libpthread is also buggy and doesn't return ESRCH on
- subsequent calls. (If libpthread isn't thusly buggy, then the
- wrapper for pthread_join in hg_intercepts.c will stop us getting
- notified here multiple times for the same joinee.) See also
- comments in helgrind/tests/jointwice.c. */
- libhb_joinedwith_done(hbthr_q);
+ generate_quitter_stayer_dependence (hbthr_q, hbthr_s);
/* evh__pre_thread_ll_exit issues an error message if the exiting
thread holds any locks. No need to check here. */
@@ -4740,6 +4747,26 @@
}
}
+/* A list of Ada dependent tasks and their masters. Used for implementing
+ the Ada task termination semantic as implemented by the
+ gcc gnat Ada runtime. */
+typedef
+ struct {
+ void* dependent; // Ada Task Control Block of the Dependent
+ void* master; // ATCB of the master
+ Word master_level; // level of dependency between master and dependent
+ Thread* hg_dependent; // helgrind Thread* for dependent task.
+ }
+ GNAT_dmml;
+static XArray* gnat_dmmls; /* of GNAT_dmml */
+static void gnat_dmmls_INIT (void)
+{
+ if (UNLIKELY(gnat_dmmls == NULL)) {
+ gnat_dmmls = VG_(newXA) (HG_(zalloc), "hg.gnat_md.1",
+ HG_(free),
+ sizeof(GNAT_dmml) );
+ }
+}
static void print_monitor_help ( void )
{
VG_(gdb_printf)
@@ -4936,6 +4963,60 @@
break;
}
+ /* This thread (tid) is informing us of its master. */
+ case _VG_USERREQ__HG_GNAT_MASTER_HOOK: {
+ GNAT_dmml dmml;
+ dmml.dependent = (void*)args[1];
+ dmml.master = (void*)args[2];
+ dmml.master_level = (Word)args[3];
+ dmml.hg_dependent = map_threads_maybe_lookup( tid );
+ tl_assert(dmml.hg_dependent);
+
+ if (0)
+ VG_(printf)("HG_GNAT_MASTER_HOOK (tid %d): "
+ "dependent = %p master = %p master_level = %ld"
+ " dependent Thread* = %p\n",
+ (Int)tid, dmml.dependent, dmml.master, dmml.master_level,
+ dmml.hg_dependent);
+ gnat_dmmls_INIT();
+ VG_(addToXA) (gnat_dmmls, &dmml);
+ break;
+ }
+
+ /* This thread (tid) is informing us that it has completed a
+ master. */
+ case _VG_USERREQ__HG_GNAT_MASTER_COMPLETED_HOOK: {
+ Word n;
+ const Thread *stayer = map_threads_maybe_lookup( tid );
+ const void *master = (void*)args[1];
+ const Word master_level = (Word) args[2];
+ tl_assert(stayer);
+
+ if (0)
+ VG_(printf)("HG_GNAT_MASTER_COMPLETED_HOOK (tid %d): "
+ "self_id = %p master_level = %ld Thread* = %p\n",
+ (Int)tid, master, master_level, stayer);
+
+ gnat_dmmls_INIT();
+ /* Reverse loop on the array, simulating a pthread_join for
+ the Dependent tasks of the completed master, and removing
+ them from the array. */
+ for (n = VG_(sizeXA) (gnat_dmmls) - 1; n >= 0; n--) {
+ GNAT_dmml *dmml = (GNAT_dmml*) VG_(indexXA)(gnat_dmmls, n);
+ if (dmml->master == master
+ && dmml->master_level == master_level) {
+ if (0)
+ VG_(printf)("quitter %p dependency to stayer %p\n",
+ dmml->hg_dependent->hbthr, stayer->hbthr);
+ tl_assert(dmml->hg_dependent->hbthr != stayer->hbthr);
+ generate_quitter_stayer_dependence (dmml->hg_dependent->hbthr,
+ stayer->hbthr);
+ VG_(removeIndexXA) (gnat_dmmls, n);
+ }
+ }
+ break;
+ }
+
/* EXPOSITION only: by intercepting lock init events we can show
the user where the lock was initialised, rather than only
being able to show where it was first locked. Intercepting
|
|
From: <sv...@va...> - 2014-06-16 18:29:02
|
Author: philippe
Date: Mon Jun 16 18:28:51 2014
New Revision: 14045
Log:
Announce in NEWS 199144 == 278972
Modified:
trunk/NEWS
Modified: trunk/NEWS
==============================================================================
--- trunk/NEWS (original)
+++ trunk/NEWS Mon Jun 16 18:28:51 2014
@@ -77,8 +77,9 @@
where XXXXXX is the bug number as listed below.
175819 Support for ipv6 socket reporting with --track-fds
+199144 == 278972
232510 make distcheck fails
-278972 valgrind stacktraces and suppression do not handle inlined function call debuginfo
+278972 support for inlined function calls in stacktraces and suppression
308729 vex x86->IR: unhandled instruction bytes 0xf 0x5 (syscall)
325110 Add test-cases for Power ISA 2.06 insns: divdo/divdo. and divduo/divduo.
325124 [MIPSEL] Compilation error
|
|
From: <sv...@va...> - 2014-06-16 18:08:15
|
Author: philippe
Date: Mon Jun 16 18:08:02 2014
New Revision: 14044
Log:
Fix random crash due to non-init inlparser when --read-var-info given but not --read-inline-info
Wrong place for the assertion for the inlparser
+ move the "zero the parsers" out of the "if VG_(clo*)" conditions
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 Mon Jun 16 18:08:02 2014
@@ -4047,6 +4047,11 @@
TRACE_SYMTAB("\n");
}
+ /* Zero out all parsers. Parsers will really be initialised
+ according to VG_(clo_read_*_info). */
+ VG_(memset)( &varparser, 0, sizeof(varparser) );
+ VG_(memset)( &inlparser, 0, sizeof(inlparser) );
+ VG_(memset)( &typarser, 0, sizeof(typarser) );
if (VG_(clo_read_var_info)) {
/* We'll park the harvested type information in here. Also create
@@ -4099,7 +4104,6 @@
types. It'll be discarded as soon as we've completed the CU,
since the resulting information is tipped in to 'tyents' as it
is generated. */
- VG_(memset)( &typarser, 0, sizeof(typarser) );
typarser.sp = -1;
typarser.language = '?';
for (i = 0; i < N_D3_TYPE_STACK; i++) {
@@ -4107,15 +4111,11 @@
typarser.qparentE[i].cuOff = D3_INVALID_CUOFF;
}
- VG_(memset)( &varparser, 0, sizeof(varparser) );
varparser.sp = -1;
signature_types = VG_(HT_construct) ("signature_types");
}
- if (VG_(clo_read_inline_info))
- VG_(memset)( &inlparser, 0, sizeof(inlparser) );
-
/* Do an initial pass to scan the .debug_types section, if any, and
fill in the signatured types hash table. This lets us handle
mapping from a type signature to a (cooked) DIE offset directly
@@ -4371,9 +4371,9 @@
vg_assert(varparser.filenameTable );
VG_(deleteXA)( varparser.filenameTable );
varparser.filenameTable = NULL;
- vg_assert(inlparser.filenameTable );
}
if (VG_(clo_read_inline_info)) {
+ vg_assert(inlparser.filenameTable );
VG_(deleteXA)( inlparser.filenameTable );
inlparser.filenameTable = NULL;
}
|
|
From: Mischenkov A. <a.m...@ya...> - 2014-06-16 17:13:02
|
I've tried to modify Valgrind Lackey tool for getting addresses of array elements in my profiled program. I try to write simple memory access profiler, that stores in file two types of memory accesses: LOADs and STOREs. After getting that I want to calculate spatial and temporal localities. I use Lackey with command line option --trace-mem=yes. In my opinion, there are two suitable functions for it: trace_load() and trace_store(), but when I've ran my profiler with test program (vector[100] * vector[100]), I got the same trace addresses in my log. How can I fix it? (Sorry for my English) Anatoliy Mischenkov |
|
From: Philippe W. <phi...@sk...> - 2014-06-16 05:02:03
|
valgrind revision: 14043 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-15 20:00:09 PDT Ended at 2014-06-15 21:58:38 PDT 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 == 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) ================================================= == 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 == 581 tests, 8 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/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) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Jun 15 20:35:25 2014 --- new.short Sun Jun 15 21:04:36 2014 *************** *** 8,10 **** ! == 581 tests, 8 stderr failures, 3 stdout failures, 0 stderrB failures, 0 stdoutB failures, 2 post failures == memcheck/tests/linux/getregset (stdout) --- 8,10 ---- ! == 584 tests, 9 stderr failures, 3 stdout failures, 0 stderrB failures, 0 stdoutB failures, 2 post failures == memcheck/tests/linux/getregset (stdout) *************** *** 14,15 **** --- 14,16 ---- memcheck/tests/varinfo6 (stderr) + memcheck/tests/vbit-test/vbit-test (stderr) memcheck/tests/wrap8 (stdout) --tools=none,memcheck,callgrind,helgrind,cachegrind,drd,massif --reps=3 --vg=../valgrind-new --vg=../valgrind-old -- Running tests in perf ---------------------------------------------- -- bigcode1 -- bigcode1 valgrind-new:0.23s no: 1.7s ( 7.3x, -----) me: 3.1s (13.6x, -----) ca:20.4s (88.8x, -----) he: 1.8s ( 7.6x, -----) ca: 5.3s (23.2x, -----) dr: 1.7s ( 7.3x, -----) ma: 2.1s ( 9.3x, -----) bigcode1 valgrind-old:0.23s no: 1.6s ( 6.8x, 7.7%) me: 2.9s (12.4x, 8.3%) ca:18.8s (81.7x, 8.0%) he: 1.8s ( 7.6x, 0.0%) ca: 5.4s (23.4x, -0.7%) dr: 1.7s ( 7.3x, -1.2%) ma: 2.1s ( 9.3x, 0.0%) -- bigcode2 -- bigcode2 valgrind-new:0.26s no: 1.6s ( 6.0x, -----) me: 3.0s (11.4x, -----) ca:20.7s (79.6x, -----) he: 2.1s ( 8.1x, -----) ca: 5.5s (21.0x, -----) dr: 1.9s ( 7.1x, -----) ma: 2.2s ( 8.3x, -----) bigcode2 valgrind-old:0.26s no: 1.6s ( 6.0x, 0.0%) me: 2.9s (11.2x, 1.7%) ca:19.1s (73.6x, 7.5%) he: 2.1s ( 8.1x, 0.0%) ca: 5.5s (21.2x, -1.3%) dr: 1.8s ( 7.1x, 0.5%) ma: 2.1s ( 8.3x, 0.9%) -- bz2 -- bz2 valgrind-new:0.72s no: 4.6s ( 6.4x, -----) me:11.6s (16.1x, -----) ca:28.5s (39.5x, -----) he:14.9s (20.7x, -----) ca:24.2s (33.7x, -----) dr:19.1s (26.5x, -----) ma: 4.7s ( 6.5x, -----) bz2 valgrind-old:0.72s no: 4.5s ( 6.3x, 0.9%) me:11.7s (16.3x, -1.1%) ca:26.4s (36.7x, 7.1%) he:14.6s (20.2x, 2.0%) ca:24.3s (33.7x, -0.1%) dr:19.0s (26.4x, 0.1%) ma: 4.7s ( 6.5x, -0.6%) -- fbench -- fbench valgrind-new:0.34s no: 2.1s ( 6.3x, -----) me: 5.2s (15.4x, -----) ca: 9.0s (26.4x, -----) he: 5.3s (15.6x, -----) ca: 7.5s (22.2x, -----) dr: 4.8s (14.2x, -----) ma: 2.2s ( 6.4x, -----) fbench valgrind-old:0.34s no: 2.1s ( 6.2x, 0.9%) me: 5.2s (15.2x, 1.1%) ca: 8.8s (26.0x, 1.8%) he: 5.3s (15.6x, 0.0%) ca: 7.5s (22.2x, 0.0%) dr: 4.8s (14.1x, 0.2%) ma: 2.1s ( 6.3x, 1.4%) -- ffbench -- ffbench valgrind-new:0.44s no: 1.3s ( 3.0x, -----) me: 2.5s ( 5.7x, -----) ca: 2.7s ( 6.2x, -----) he: 6.9s (15.6x, -----) ca: 6.8s (15.6x, -----) dr: 5.0s (11.2x, -----) ma: 1.1s ( 2.5x, -----) ffbench valgrind-old:0.44s no: 1.3s ( 3.0x, 0.0%) me: 2.5s ( 5.6x, 0.4%) ca: 2.5s ( 5.8x, 7.0%) he: 7.0s (16.0x, -2.6%) ca: 7.0s (15.8x, -1.8%) dr: 4.9s (11.2x, 0.8%) ma: 1.1s ( 2.5x, 0.9%) -- heap -- heap valgrind-new:0.41s no: 2.5s ( 6.0x, -----) me: 9.7s (23.6x, -----) ca:14.2s (34.6x, -----) he:11.9s (29.0x, -----) ca:12.1s (29.4x, -----) dr: 8.2s (19.9x, -----) ma: 8.5s (20.8x, -----) heap valgrind-old:0.41s no: 2.5s ( 6.0x, 0.0%) me: 9.4s (23.0x, 2.4%) ca:13.6s (33.2x, 4.1%) he:11.8s (28.8x, 0.4%) ca:12.1s (29.5x, -0.4%) dr: 8.4s (20.6x, -3.4%) ma: 8.5s (20.8x, 0.0%) -- heap_pdb4 -- heap_pdb4 valgrind-new:0.42s no: 2.5s ( 6.0x, -----) me:13.6s (32.5x, -----) ca:15.2s (36.2x, -----) he:13.3s (31.7x, -----) ca:13.1s (31.2x, -----) dr: 9.0s (21.5x, -----) ma: 8.8s (20.9x, -----) heap_pdb4 valgrind-old:0.42s no: 2.6s ( 6.1x, -2.0%) me:13.6s (32.4x, 0.3%) ca:14.6s (34.9x, 3.7%) he:13.2s (31.4x, 1.1%) ca:13.1s (31.2x, -0.2%) dr: 9.0s (21.5x, 0.1%) ma: 8.7s (20.8x, 0.7%) -- many-loss-records -- many-loss-records valgrind-new:0.03s no: 0.5s (17.7x, -----) me: 2.2s (72.3x, -----) ca: 2.0s (66.7x, -----) he: 1.8s (60.7x, -----) ca: 1.9s (62.0x, -----) dr: 1.6s (51.7x, -----) ma: 1.6s (52.0x, -----) many-loss-records valgrind-old:0.03s no: 0.5s (18.0x, -1.9%) me: 2.1s (71.0x, 1.8%) ca: 2.0s (65.7x, 1.5%) he: 1.8s (60.3x, 0.5%) ca: 1.9s (62.0x, 0.0%) dr: 1.6s (53.3x, -3.2%) ma: 1.6s (51.7x, 0.6%) -- many-xpts -- many-xpts valgrind-new:0.07s no: 0.8s (10.7x, -----) me: 3.4s (48.4x, -----) ca: 5.0s (70.7x, -----) he: 4.8s (69.0x, -----) ca: 2.9s (41.4x, -----) dr: 2.3s (32.7x, -----) ma: 2.3s (32.4x, -----) many-xpts valgrind-old:0.07s no: 0.8s (10.7x, 0.0%) me: 3.3s (47.4x, 2.1%) ca: 4.9s (70.6x, 0.2%) he: 4.9s (69.4x, -0.6%) ca: 2.9s (41.3x, 0.3%) dr: 2.3s (33.4x, -2.2%) ma: 2.3s (33.3x, -2.6%) -- sarp -- sarp valgrind-new:0.02s no: 0.4s (21.0x, -----) me: 3.1s (154.5x, -----) ca: 3.1s (156.0x, -----) he:11.0s (548.0x, -----) ca: 1.8s (92.0x, -----) dr: 1.1s (53.5x, -----) ma: 0.4s (21.0x, -----) sarp valgrind-old:0.02s no: 0.4s (21.5x, -2.4%) me: 3.1s (154.5x, 0.0%) ca: 3.2s (158.0x, -1.3%) he:11.2s (561.0x, -2.4%) ca: 1.7s (85.5x, 7.1%) dr: 1.1s (53.5x, 0.0%) ma: 0.4s (21.0x, 0.0%) -- tinycc -- tinycc valgrind-new:0.27s no: 3.0s (11.0x, -----) me:13.7s (50.8x, -----) ca:18.4s (68.2x, -----) he:18.9s (70.0x, -----) ca:15.7s (58.0x, -----) dr:12.0s (44.3x, -----) ma: 3.8s (14.1x, -----) tinycc valgrind-old:0.27s no: 3.0s (11.0x, 0.0%) me:13.7s (50.9x, -0.1%) ca:17.9s (66.4x, 2.6%) he:18.9s (70.2x, -0.3%) ca:15.6s (57.9x, 0.1%) dr:12.0s (44.6x, -0.7%) ma: 3.8s (14.1x, -0.3%) -- Finished tests in perf ---------------------------------------------- == 11 programs, 154 timings ================= real 54m1.962s user 52m53.945s sys 0m19.016s |
|
From: Christian B. <bor...@de...> - 2014-06-16 04:13:37
|
valgrind revision: 14043 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-16 03:45:01 CEST Ended at 2014-06-16 06:13:22 CEST 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 == 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) ================================================= == 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 == 647 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == helgrind/tests/pth_cond_destroy_busy (stderr) helgrind/tests/tc20_verifywrap (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Mon Jun 16 04:03:46 2014 --- new.short Mon Jun 16 04:20:44 2014 *************** *** 8,10 **** ! == 647 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == helgrind/tests/pth_cond_destroy_busy (stderr) --- 8,11 ---- ! == 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) --tools=none,memcheck,callgrind,helgrind,cachegrind,drd,massif --reps=3 --vg=../valgrind-new --vg=../valgrind-old -- Running tests in perf ---------------------------------------------- -- bigcode1 -- bigcode1 valgrind-new:0.23s no: 4.3s (18.7x, -----) me: 6.9s (30.0x, -----) ca:26.4s (114.7x, -----) he: 5.1s (22.1x, -----) ca: 9.2s (39.8x, -----) dr: 5.4s (23.4x, -----) ma: 5.0s (21.6x, -----) bigcode1 valgrind-old:0.23s no: 4.4s (19.0x, -1.2%) me: 6.9s (30.0x, -0.3%) ca:26.4s (114.7x, -0.0%) he: 5.1s (22.0x, 0.2%) ca: 9.1s (39.7x, 0.1%) dr: 5.4s (23.4x, 0.0%) ma: 4.6s (20.1x, 7.0%) -- bigcode2 -- bigcode2 valgrind-new:0.24s no: 7.3s (30.3x, -----) me:13.8s (57.5x, -----) ca:39.5s (164.5x, -----) he:10.1s (41.9x, -----) ca:14.3s (59.5x, -----) dr: 9.5s (39.6x, -----) ma: 8.4s (35.0x, -----) bigcode2 valgrind-old:0.24s no: 7.3s (30.5x, -0.6%) me:13.8s (57.6x, -0.1%) ca:39.6s (165.0x, -0.3%) he:10.0s (41.8x, 0.1%) ca:14.3s (59.5x, 0.1%) dr: 9.6s (40.0x, -0.8%) ma: 8.2s (34.3x, 2.0%) -- bz2 -- bz2 valgrind-new:0.70s no: 5.0s ( 7.1x, -----) me:12.8s (18.2x, -----) ca:30.7s (43.8x, -----) he:19.6s (28.0x, -----) ca:34.3s (49.0x, -----) dr:29.2s (41.7x, -----) ma: 4.7s ( 6.7x, -----) bz2 valgrind-old:0.70s no: 5.1s ( 7.3x, -1.8%) me:12.7s (18.2x, 0.4%) ca:30.6s (43.7x, 0.2%) he:19.6s (28.0x, 0.1%) ca:34.3s (49.1x, -0.1%) dr:31.7s (45.3x, -8.8%) ma: 3.9s ( 5.6x, 15.8%) -- fbench -- fbench valgrind-new:0.41s no: 1.6s ( 4.0x, -----) me: 4.2s (10.3x, -----) ca: 9.3s (22.7x, -----) he: 6.2s (15.2x, -----) ca: 7.2s (17.5x, -----) dr: 5.5s (13.5x, -----) ma: 1.7s ( 4.1x, -----) fbench valgrind-old:0.41s no: 1.6s ( 3.9x, 0.6%) me: 4.2s (10.3x, -0.2%) ca: 9.3s (22.7x, 0.0%) he: 6.2s (15.2x, -0.2%) ca: 7.2s (17.5x, 0.0%) dr: 5.8s (14.2x, -5.6%) ma: 1.7s ( 4.1x, 0.0%) -- ffbench -- ffbench valgrind-new:0.21s no: 1.1s ( 5.2x, -----) me: 3.0s (14.5x, -----) ca: 3.0s (14.5x, -----) he:44.2s (210.4x, -----) ca: 9.6s (45.9x, -----) dr: 6.9s (33.0x, -----) ma: 1.0s ( 4.7x, -----) ffbench valgrind-old:0.21s no: 1.1s ( 5.1x, 1.8%) me: 3.0s (14.2x, 2.3%) ca: 3.0s (14.3x, 1.3%) he:44.1s (210.0x, 0.2%) ca: 9.6s (45.9x, -0.1%) dr: 7.1s (33.7x, -2.0%) ma: 1.0s ( 4.6x, 1.0%) -- heap -- heap valgrind-new:0.23s no: 1.9s ( 8.3x, -----) me: 8.8s (38.1x, -----) ca:13.2s (57.3x, -----) he:12.8s (55.7x, -----) ca:11.3s (49.1x, -----) dr: 7.7s (33.5x, -----) ma: 8.0s (34.6x, -----) heap valgrind-old:0.23s no: 1.9s ( 8.1x, 1.6%) me: 8.6s (37.4x, 1.9%) ca:13.2s (57.3x, -0.1%) he:12.8s (55.5x, 0.2%) ca:11.4s (49.5x, -0.9%) dr: 8.3s (36.2x, -7.9%) ma: 8.1s (35.0x, -1.3%) -- heap_pdb4 -- heap_pdb4 valgrind-new:0.22s no: 2.1s ( 9.5x, -----) me:12.9s (58.9x, -----) ca:14.2s (64.4x, -----) he:14.1s (64.1x, -----) ca:12.3s (56.1x, -----) dr: 8.7s (39.5x, -----) ma: 8.1s (37.0x, -----) heap_pdb4 valgrind-old:0.22s no: 2.0s ( 9.3x, 2.4%) me:12.7s (57.8x, 1.8%) ca:14.2s (64.4x, 0.0%) he:13.9s (63.0x, 1.6%) ca:12.4s (56.2x, -0.2%) dr: 9.2s (41.6x, -5.3%) ma: 8.1s (36.6x, 0.9%) -- many-loss-records -- many-loss-records valgrind-new:0.02s no: 0.5s (24.5x, -----) me: 2.1s (104.5x, -----) ca: 1.9s (97.5x, -----) he: 2.2s (108.0x, -----) ca: 1.9s (96.0x, -----) dr: 1.7s (87.0x, -----) ma: 1.7s (85.0x, -----) many-loss-records valgrind-old:0.02s no: 0.5s (24.5x, 0.0%) me: 2.1s (103.5x, 1.0%) ca: 1.9s (97.5x, 0.0%) he: 2.1s (106.0x, 1.9%) ca: 1.9s (95.5x, 0.5%) dr: 1.8s (90.5x, -4.0%) ma: 1.7s (85.0x, 0.0%) -- many-xpts -- many-xpts valgrind-new:0.07s no: 0.7s ( 9.3x, -----) me: 3.2s (45.3x, -----) ca:388.4s (5547.9x, -----) he: 6.5s (92.9x, -----) ca: 2.8s (40.0x, -----) dr: 2.5s (35.9x, -----) ma: 2.7s (38.0x, -----) many-xpts valgrind-old:0.07s no: 0.6s ( 9.1x, 1.5%) me: 3.1s (44.7x, 1.3%) ca:378.7s (5410.1x, 2.5%) he: 6.5s (92.1x, 0.8%) ca: 2.8s (39.9x, 0.4%) dr: 2.6s (37.3x, -4.0%) ma: 2.6s (37.9x, 0.4%) -- sarp -- sarp valgrind-new:0.03s no: 0.6s (19.0x, -----) me: 3.4s (114.3x, -----) ca: 3.1s (104.7x, -----) he:16.3s (543.7x, -----) ca: 2.1s (68.7x, -----) dr: 1.4s (45.3x, -----) ma: 0.5s (17.3x, -----) sarp valgrind-old:0.03s no: 0.6s (19.3x, -1.8%) me: 3.4s (114.3x, 0.0%) ca: 3.1s (104.7x, 0.0%) he:16.8s (561.0x, -3.2%) ca: 2.0s (68.3x, 0.5%) dr: 1.6s (53.3x,-17.6%) ma: 0.5s (16.3x, 5.8%) -- tinycc -- tinycc valgrind-new:0.22s no: 2.8s (12.8x, -----) me:14.5s (65.8x, -----) ca:30.1s (136.8x, -----) he:27.7s (125.8x, -----) ca:21.5s (97.5x, -----) dr:20.6s (93.6x, -----) ma: 4.1s (18.6x, -----) tinycc valgrind-old:0.22s no: 2.8s (12.9x, -0.7%) me:14.5s (65.7x, 0.1%) ca:30.3s (137.6x, -0.6%) he:27.7s (125.8x, 0.0%) ca:21.5s (97.8x, -0.2%) dr:22.1s (100.6x, -7.5%) ma: 4.0s (18.2x, 2.2%) -- Finished tests in perf ---------------------------------------------- == 11 programs, 154 timings ================= real 112m38.778s user 111m31.226s sys 0m54.597s |
|
From: Tom H. <to...@co...> - 2014-06-16 03:28:51
|
valgrind revision: 14043 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-16 03:51:16 BST Ended at 2014-06-16 04:28:33 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 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) ================================================= == 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 == 650 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/amd64/insn-pcmpistri (stderr) memcheck/tests/err_disable4 (stderr) none/tests/amd64/sse4-64 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short 2014-06-16 04:08:44.038505988 +0100 --- new.short 2014-06-16 04:28:33.245295237 +0100 *************** *** 8,12 **** ! == 650 tests, 2 stderr failures, 1 stdout failure, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/amd64/insn-pcmpistri (stderr) memcheck/tests/err_disable4 (stderr) none/tests/amd64/sse4-64 (stdout) --- 8,13 ---- ! == 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-16 03:10:36
|
valgrind revision: 14043 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-15 21:30:01 CDT Ended at 2014-06-15 22:10:21 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, 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) ================================================= == 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 == 674 tests, 0 stderr failures, 0 stdout failures, 2 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/hginfo (stderrB) gdbserver_tests/mssnapshot (stderrB) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Jun 15 21:50:57 2014 --- new.short Sun Jun 15 22:10:21 2014 *************** *** 8,12 **** ! == 674 tests, 0 stderr failures, 0 stdout failures, 2 stderrB failures, 0 stdoutB failures, 0 post failures == gdbserver_tests/hginfo (stderrB) gdbserver_tests/mssnapshot (stderrB) --- 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) ================================================= ./valgrind-new/drd/tests/annotate_barrier.stderr.diff ================================================= --- annotate_barrier.stderr.exp 2014-06-15 21:54:17.109100409 -0500 +++ annotate_barrier.stderr.out 2014-06-15 22:08:48.135410073 -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-new/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-new/drd/tests/annotate_barrier_xml.stderr.diff ================================================= --- annotate_barrier_xml.stderr.exp 2014-06-15 21:54:17.104100544 -0500 +++ annotate_barrier_xml.stderr.out 2014-06-15 22:08:48.205408148 -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-new/drd/tests/annotate_hb_err.stderr.diff ================================================= --- annotate_hb_err.stderr.exp 2014-06-15 21:54:17.037102355 -0500 +++ annotate_hb_err.stderr.out 2014-06-15 22:08:48.263406553 -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-new/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-new/drd/tests/annotate_hbefore.stderr.diff ================================================= --- annotate_hbefore.stderr.exp 2014-06-15 21:54:17.039102301 -0500 +++ annotate_hbefore.stderr.out 2014-06-15 22:08:48.803391701 -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-new/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-new/drd/tests/annotate_ignore_read.stderr.diff ================================================= --- annotate_ignore_read.stderr.exp 2014-06-15 21:54:17.100100652 -0500 +++ annotate_ignore_read.stderr.out 2014-06-15 22:08:48.868389914 -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-new/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-new/drd/tests/annotate_ignore_rw.stderr.diff ================================================= --- annotate_ignore_rw.stderr.exp 2014-06-15 21:54:17.089100950 -0500 +++ annotate_ignore_rw.stderr.out 2014-06-15 22:08:48.907388841 -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-new/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-new/drd/tests/annotate_ignore_rw2.stderr.diff ================================================= --- annotate_ignore_rw2.stderr.exp 2014-06-15 21:54:17.023102734 -0500 +++ annotate_ignore_rw2.stderr.out 2014-06-15 22:08:48.950387659 -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-new/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-new/drd/tests/annotate_ignore_write.stderr.diff ================================================= --- annotate_ignore_write.stderr.exp 2014-06-15 21:54:17.035102409 -0500 +++ annotate_ignore_write.stderr.out 2014-06-15 22:08:48.986386669 -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-new/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-new/drd/tests/annotate_ignore_write2.stderr.diff ================================================= --- annotate_ignore_write2.stderr.exp 2014-06-15 21:54:17.092100869 -0500 +++ annotate_ignore_write2.stderr.out 2014-06-15 22:08:49.021385706 -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-new/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-new/drd/tests/annotate_order_1.stderr.diff ================================================= --- annotate_order_1.stderr.exp 2014-06-15 21:54:17.034102436 -0500 +++ annotate_order_1.stderr.out 2014-06-15 22:08:49.069384386 -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-new/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-new/drd/tests/annotate_order_2.stderr.diff ================================================= --- annotate_order_2.stderr.exp 2014-06-15 21:54:17.110100382 -0500 +++ annotate_order_2.stderr.out 2014-06-15 22:08:49.113383176 -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-new/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-new/drd/tests/annotate_order_3.stderr.diff ================================================= --- annotate_order_3.stderr.exp 2014-06-15 21:54:17.074101355 -0500 +++ annotate_order_3.stderr.out 2014-06-15 22:08:49.159381911 -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-new/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-new/drd/tests/annotate_publish_hg.stderr.diff ================================================= --- annotate_publish_hg.stderr.exp 2014-06-15 21:54:17.078101247 -0500 +++ annotate_publish_hg.stderr.out 2014-06-15 22:08:49.205380646 -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-new/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-new/drd/tests/annotate_rwlock.stderr.diff ================================================= --- annotate_rwlock.stderr.exp 2014-06-15 21:54:17.055101869 -0500 +++ annotate_rwlock.stderr.out 2014-06-15 22:08:49.250379408 -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-new/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-new/drd/tests/annotate_rwlock_hg.stderr.diff ================================================= --- annotate_rwlock_hg.stderr.exp 2014-06-15 21:54:17.115100247 -0500 +++ annotate_rwlock_hg.stderr.out 2014-06-15 22:08:49.272378803 -0500 @@ -1 +0,0 @@ -Total error count is below threshold. ================================================= ./valgrind-new/drd/tests/annotate_sem.stderr.diff ================================================= --- annotate_sem.stderr.exp 2014-06-15 21:54:17.041102247 -0500 +++ annotate_sem.stderr.out 2014-06-15 22:08:49.324377373 -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-new/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-new/drd/tests/annotate_smart_pointer.stderr.diff ================================================= --- annotate_smart_pointer.stderr.exp 2014-06-15 21:54:17.100100652 -0500 +++ annotate_smart_pointer.stderr.out 2014-06-15 22:08:49.382375778 -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-new/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-new/drd/tests/annotate_smart_pointer2.stderr.diff ================================================= --- annotate_smart_pointer2.stderr.exp 2014-06-15 21:54:17.112100328 -0500 +++ annotate_smart_pointer2.stderr.out 2014-06-15 22:08:49.424374623 -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-new/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-new/drd/tests/annotate_smart_pointer2.stderr.diff-darwin ================================================= --- annotate_smart_pointer2.stderr.exp-darwin 2014-06-15 21:54:17.053101923 -0500 +++ annotate_smart_pointer2.stderr.out 2014-06-15 22:08:49.424374623 -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-new/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-new/drd/tests/annotate_spinlock.stderr.diff ================================================= --- annotate_spinlock.stderr.exp 2014-06-15 21:54:17.025102680 -0500 +++ annotate_spinlock.stderr.out 2014-06-15 22:08:49.472373302 -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-new/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-new/drd/tests/annotate_static.stderr.diff ================================================= --- annotate_static.stderr.exp 2014-06-15 21:54:17.123100031 -0500 +++ annotate_static.stderr.out 2014-06-15 22:08:49.509372285 -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-new/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-new/drd/tests/annotate_trace_memory.stderr.diff-32bit ================================================= --- annotate_trace_memory.stderr.exp-32bit 2014-06-15 21:54:17.083101112 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 22:08:49.549371185 -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-new/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-new/drd/tests/annotate_trace_memory.stderr.diff-64bit ================================================= --- annotate_trace_memory.stderr.exp-64bit 2014-06-15 21:54:17.099100679 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 22:08:49.549371185 -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-new/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-new/drd/tests/annotate_trace_memory.stderr.diff-mips32 ================================================= --- annotate_trace_memory.stderr.exp-mips32 2014-06-15 21:54:17.020102814 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 22:08:49.549371185 -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-new/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-new/drd/tests/annotate_trace_memory_xml.stderr.diff-32bit ================================================= --- annotate_trace_memory_xml.stderr.exp-32bit 2014-06-15 21:54:17.079101220 -0500 +++ annotate_trace_memory_xml.stderr.out 2014-06-15 22:08:49.611369480 -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-new/drd/tests/annotate_trace_memory_xml.stderr.diff-64bit ================================================= --- annotate_trace_memory_xml.stderr.exp-64bit 2014-06-15 21:54:17.095100788 -0500 +++ annotate_trace_memory_xml.stderr.out 2014-06-15 22:08:49.611369480 -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> - </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> - <stack> <truncated beyond 100 lines> ================================================= ./valgrind-new/drd/tests/annotate_trace_memory_xml.stderr.diff-mips32 ================================================= --- annotate_trace_memory_xml.stderr.exp-mips32 2014-06-15 21:54:17.130099842 -0500 +++ annotate_trace_memory_xml.stderr.out 2014-06-15 22:08:49.611369480 -0500 @@ -23,316 +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... [truncated message content] |
|
From: Tom H. <to...@co...> - 2014-06-16 02:40:42
|
valgrind revision: 14043 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-16 03:02:03 BST Ended at 2014-06-16 03:40:30 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 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) ================================================= == 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 == 681 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short 2014-06-16 03:21:16.653067302 +0100 --- new.short 2014-06-16 03:40:30.817510030 +0100 *************** *** 8,11 **** ! == 681 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable4 (stderr) --- 8,12 ---- ! == 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: Rich C. <rc...@wi...> - 2014-06-16 02:16:07
|
valgrind revision: 14043 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-15 19:22:01 CDT Ended at 2014-06-15 21:15:58 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, 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) ================================================= == 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 == 596 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable3 (stderr) memcheck/tests/err_disable4 (stderr) memcheck/tests/threadname (stderr) memcheck/tests/threadname_xml (stderr) exp-sgcheck/tests/hackedbz2 (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Jun 15 20:31:54 2014 --- new.short Sun Jun 15 21:15:58 2014 *************** *** 8,10 **** ! == 596 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/err_disable3 (stderr) --- 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) *************** *** 13,15 **** --- 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) ================================================= ./valgrind-new/drd/tests/annotate_barrier.stderr.diff ================================================= --- annotate_barrier.stderr.exp 2014-06-15 20:37:07.242128281 -0500 +++ annotate_barrier.stderr.out 2014-06-15 21:12:04.278454852 -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-new/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-new/drd/tests/annotate_barrier_xml.stderr.diff ================================================= --- annotate_barrier_xml.stderr.exp 2014-06-15 20:37:07.230128142 -0500 +++ annotate_barrier_xml.stderr.out 2014-06-15 21:12:04.495457369 -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-new/drd/tests/annotate_hb_err.stderr.diff ================================================= --- annotate_hb_err.stderr.exp 2014-06-15 20:37:07.267128571 -0500 +++ annotate_hb_err.stderr.out 2014-06-15 21:12:04.663459318 -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-new/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-new/drd/tests/annotate_hbefore.stderr.diff ================================================= --- annotate_hbefore.stderr.exp 2014-06-15 20:37:07.082126425 -0500 +++ annotate_hbefore.stderr.out 2014-06-15 21:12:06.763483679 -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-new/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-new/drd/tests/annotate_ignore_read.stderr.diff ================================================= --- annotate_ignore_read.stderr.exp 2014-06-15 20:37:07.220128026 -0500 +++ annotate_ignore_read.stderr.out 2014-06-15 21:12:07.125487879 -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-new/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-new/drd/tests/annotate_ignore_rw.stderr.diff ================================================= --- annotate_ignore_rw.stderr.exp 2014-06-15 20:37:07.075126344 -0500 +++ annotate_ignore_rw.stderr.out 2014-06-15 21:12:07.294489839 -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-new/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-new/drd/tests/annotate_ignore_rw2.stderr.diff ================================================= --- annotate_ignore_rw2.stderr.exp 2014-06-15 20:37:07.237128223 -0500 +++ annotate_ignore_rw2.stderr.out 2014-06-15 21:12:07.420491301 -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-new/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-new/drd/tests/annotate_ignore_write.stderr.diff ================================================= --- annotate_ignore_write.stderr.exp 2014-06-15 20:37:07.132127005 -0500 +++ annotate_ignore_write.stderr.out 2014-06-15 21:12:07.562492948 -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-new/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-new/drd/tests/annotate_ignore_write2.stderr.diff ================================================= --- annotate_ignore_write2.stderr.exp 2014-06-15 20:37:07.083126436 -0500 +++ annotate_ignore_write2.stderr.out 2014-06-15 21:12:07.687494398 -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-new/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-new/drd/tests/annotate_order_1.stderr.diff ================================================= --- annotate_order_1.stderr.exp 2014-06-15 20:37:07.076126355 -0500 +++ annotate_order_1.stderr.out 2014-06-15 21:12:07.848496266 -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-new/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-new/drd/tests/annotate_order_2.stderr.diff ================================================= --- annotate_order_2.stderr.exp 2014-06-15 20:37:07.246128327 -0500 +++ annotate_order_2.stderr.out 2014-06-15 21:12:08.017498227 -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-new/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-new/drd/tests/annotate_order_3.stderr.diff ================================================= --- annotate_order_3.stderr.exp 2014-06-15 20:37:07.162127353 -0500 +++ annotate_order_3.stderr.out 2014-06-15 21:12:08.182500141 -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-new/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-new/drd/tests/annotate_publish_hg.stderr.diff ================================================= --- annotate_publish_hg.stderr.exp 2014-06-15 20:37:07.109126738 -0500 +++ annotate_publish_hg.stderr.out 2014-06-15 21:12:08.363502240 -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-new/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-new/drd/tests/annotate_rwlock.stderr.diff ================================================= --- annotate_rwlock.stderr.exp 2014-06-15 20:37:07.061126181 -0500 +++ annotate_rwlock.stderr.out 2014-06-15 21:12:08.513503980 -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-new/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-new/drd/tests/annotate_rwlock_hg.stderr.diff ================================================= --- annotate_rwlock_hg.stderr.exp 2014-06-15 20:37:07.123126901 -0500 +++ annotate_rwlock_hg.stderr.out 2014-06-15 21:12:08.577504723 -0500 @@ -1 +0,0 @@ -Total error count is below threshold. ================================================= ./valgrind-new/drd/tests/annotate_sem.stderr.diff ================================================= --- annotate_sem.stderr.exp 2014-06-15 20:37:07.087126483 -0500 +++ annotate_sem.stderr.out 2014-06-15 21:12:08.726506451 -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-new/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-new/drd/tests/annotate_smart_pointer.stderr.diff ================================================= --- annotate_smart_pointer.stderr.exp 2014-06-15 20:37:07.098126610 -0500 +++ annotate_smart_pointer.stderr.out 2014-06-15 21:12:08.867508087 -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-new/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-new/drd/tests/annotate_smart_pointer2.stderr.diff ================================================= --- annotate_smart_pointer2.stderr.exp 2014-06-15 20:37:07.190127678 -0500 +++ annotate_smart_pointer2.stderr.out 2014-06-15 21:12:09.125511080 -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-new/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-new/drd/tests/annotate_smart_pointer2.stderr.diff-darwin ================================================= --- annotate_smart_pointer2.stderr.exp-darwin 2014-06-15 20:37:07.245128316 -0500 +++ annotate_smart_pointer2.stderr.out 2014-06-15 21:12:09.125511080 -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-new/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-new/drd/tests/annotate_spinlock.stderr.diff ================================================= --- annotate_spinlock.stderr.exp 2014-06-15 20:37:07.108126726 -0500 +++ annotate_spinlock.stderr.out 2014-06-15 21:12:09.306513180 -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-new/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-new/drd/tests/annotate_static.stderr.diff ================================================= --- annotate_static.stderr.exp 2014-06-15 20:37:07.212127933 -0500 +++ annotate_static.stderr.out 2014-06-15 21:12:09.450514850 -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-new/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-new/drd/tests/annotate_trace_memory.stderr.diff-32bit ================================================= --- annotate_trace_memory.stderr.exp-32bit 2014-06-15 20:37:07.118126843 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 21:12:09.594516521 -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-new/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-new/drd/tests/annotate_trace_memory.stderr.diff-64bit ================================================= --- annotate_trace_memory.stderr.exp-64bit 2014-06-15 20:37:07.154127260 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 21:12:09.594516521 -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-new/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-new/drd/tests/annotate_trace_memory.stderr.diff-mips32 ================================================= --- annotate_trace_memory.stderr.exp-mips32 2014-06-15 20:37:07.041125949 -0500 +++ annotate_trace_memory.stderr.out 2014-06-15 21:12:09.594516521 -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/valgrind/nightly/valgrind-new/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-new/drd/tests/annotate_trace_memory_xml.stderr.diff-32bit ================================================= --- annotate_trace_memory_xml.stderr.exp-32bit 2014-06-15 20:37:07.112126773 -0500 +++ annotate_trace_memory_xml.stderr.out 2014-06-15 21:12:09.819519131 -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-new/drd/tests/annotate_trace_memory_xml.stderr.diff-64bit ================================================= --- annotate_trace_memory_xml.stderr.exp-64bit 2014-06-15 20:37:07.147127179 -0500 +++ annotate_trace_memory_xml.stderr.out 2014-06-15 21:12:09.819519131 -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> - </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> - <stack> <truncated beyond 100 lines> ================================================= ./valgrind-new/drd/tests/annotate_trace_memory_xml.stderr.diff-mips32 ================================================= --- annotate_trace_memory_xml.stderr.exp-mips32 2014-06-15 20:37:07.294128884 -0500 +++ annotate_trace_memory_xml.... [truncated message content] |