|
From: Anmol P. <An...@fr...> - 2014-10-15 18:10:27
|
- armv7hl, glibc-2.19.90 (2.20-pre), linux-3.15.10
== 558 tests, 69 stderr failures, 7 stdout failures, 1 stderrB failure,
1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
gdbserver_tests/mcblocklistsearch (stderrB)
memcheck/tests/demangle (stderr)
memcheck/tests/dw4 (stderr)
memcheck/tests/err_disable3 (stderr)
memcheck/tests/err_disable4 (stderr)
memcheck/tests/leak-cases-full (stderr)
memcheck/tests/leak-cases-summary (stderr)
memcheck/tests/leak-cycle (stderr)
memcheck/tests/leak-segv-jmp (stderr)
memcheck/tests/leak-tree (stderr)
memcheck/tests/leak_cpp_interior (stderr)
memcheck/tests/linux/stack_changes (stderr)
memcheck/tests/linux/timerfd-syscall (stderr)
memcheck/tests/lks (stderr)
memcheck/tests/origin5-bz2 (stderr)
memcheck/tests/partiallydefinedeq (stderr)
memcheck/tests/supp_unknown (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 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/varinfo6 (stderr)
memcheck/tests/varinforestrict (stderr)
memcheck/tests/vbit-test/vbit-test (stderr)
none/tests/arm/neon128 (stdout)
none/tests/arm/neon128 (stderr)
none/tests/arm/neon64 (stdout)
none/tests/arm/neon64 (stderr)
none/tests/arm/v6intARM (stdout)
none/tests/arm/v6intThumb (stdout)
none/tests/arm/v6media (stdout)
none/tests/arm/v6media (stderr)
none/tests/arm/vcvt_fixed_float_VFP (stdout)
none/tests/arm/vcvt_fixed_float_VFP (stderr)
none/tests/arm/vfp (stdout)
none/tests/arm/vfp (stderr)
none/tests/process_vm_readv_writev (stderr)
helgrind/tests/annotate_rwlock (stderr)
helgrind/tests/free_is_write (stderr)
helgrind/tests/hg02_deadlock (stderr)
helgrind/tests/hg03_inherit (stderr)
helgrind/tests/hg04_race (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/locked_vs_unlocked1_fwd (stderr)
helgrind/tests/locked_vs_unlocked1_rev (stderr)
helgrind/tests/locked_vs_unlocked2 (stderr)
helgrind/tests/locked_vs_unlocked3 (stderr)
helgrind/tests/pth_barrier1 (stderr)
helgrind/tests/pth_barrier2 (stderr)
helgrind/tests/pth_barrier3 (stderr)
helgrind/tests/pth_cond_destroy_busy (stderr)
helgrind/tests/pth_destroy_cond (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/tc09_bad_unlock (stderr)
helgrind/tests/tc14_laog_dinphils (stderr)
helgrind/tests/tc16_byterace (stderr)
helgrind/tests/tc19_shadowmem (stderr)
helgrind/tests/tc20_verifywrap (stderr)
helgrind/tests/tc21_pthonce (stderr)
helgrind/tests/tc22_exit_w_lock (stderr)
drd/tests/annotate_trace_memory (stderr)
drd/tests/annotate_trace_memory_xml (stderr)
drd/tests/atomic_var (stderr)
drd/tests/hg03_inherit (stderr)
drd/tests/hg04_race (stderr)
drd/tests/hg05_race2 (stderr)
drd/tests/rwlock_race (stderr)
drd/tests/std_thread2 (stderr)
drd/tests/tc19_shadowmem (stderr)
drd/tests/tc21_pthonce (stderr)
[]
Hello Mark,
Please could you share the details of how glibc was configured and built for armv7hl;
We're seeing a bunch of failures (mostly) in drd - it seems like drd behaves differently
(we're using glibc-2.18-2013.10) and see, e.g.
--- annotate_barrier.stderr.exp 2014-09-08 12:28:01.000000000 +0000
+++ annotate_barrier.stderr.out 2014-10-09 15:56:47.880000000 +0000
@@ -24,8 +24,6 @@
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:?)
At this point, I am trying to first get parity on the glibc(lippthread) front - it's plausible that it has
a bearing on drd's behaviour, so I want to make sure that I'm configuring and building as you did. Any other
advice you might have for me is gratefully received too.
Thanks,
Anmol P. Paralkar
|