|
From: Christian B. <bor...@de...> - 2012-10-18 07:18:41
Attachments:
diffs.txt
|
valgrind revision: 13052 VEX revision: 2552 C compiler: gcc (GCC) 4.6.1 20110908 (Red Hat 4.6.1-9bb4) Assembler: GNU assembler version 2.21.51.0.6-6bb6.fc15 20110118 C library: GNU C Library stable release version 2.14.1 uname -mrs: Linux 3.6.1-56.x.20121010-s390xperformance s390x Vendor version: unknown Nightly build on fedora390 ( Fedora 15 with devel libc/toolchain on z196 (s390x) ) Started at 2012-10-18 03:45:01 CEST Ended at 2012-10-18 09:18:17 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 == 607 tests, 12 stderr failures, 4 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/mcclean_after_fork (stderr) gdbserver_tests/mcclean_after_fork (stdoutB) memcheck/tests/addressable (stdout) memcheck/tests/addressable (stderr) memcheck/tests/vbit-test/vbit-test (stderr) none/tests/allexec32 (stdout) none/tests/allexec32 (stderr) none/tests/allexec64 (stdout) none/tests/allexec64 (stderr) none/tests/async-sigs (stderr) none/tests/exec-sigmask (stderr) none/tests/pth_atfork1 (stdout) none/tests/pth_atfork1 (stderr) none/tests/shell (stderr) none/tests/threaded-fork (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 == 604 tests, 13 stderr failures, 4 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/mcclean_after_fork (stderr) gdbserver_tests/mcclean_after_fork (stdoutB) memcheck/tests/addressable (stdout) memcheck/tests/addressable (stderr) memcheck/tests/vbit-test/vbit-test (stderr) none/tests/allexec32 (stdout) none/tests/allexec32 (stderr) none/tests/allexec64 (stdout) none/tests/allexec64 (stderr) none/tests/async-sigs (stderr) none/tests/exec-sigmask (stderr) none/tests/pth_atfork1 (stdout) none/tests/pth_atfork1 (stderr) none/tests/shell (stderr) none/tests/threaded-fork (stderr) helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) drd/tests/threaded-fork (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Oct 18 09:07:33 2012 --- new.short Thu Oct 18 09:18:17 2012 *************** *** 8,10 **** ! == 604 tests, 13 stderr failures, 4 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/mcclean_after_fork (stderr) --- 8,10 ---- ! == 607 tests, 12 stderr failures, 4 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/mcclean_after_fork (stderr) *************** *** 26,28 **** helgrind/tests/tc20_verifywrap (stderr) - drd/tests/threaded-fork (stderr) --- 26,27 ---- |
|
From: Christian B. <bor...@de...> - 2012-10-18 08:31:57
|
Interesting, something on this box made valgrinds scheduler go wild. On programs doing fork we see +valgrind: m_scheduler/scheduler.c:545 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed. or +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed. There are some modified versions of gcc/glibc etc from our toolchain folks, but it should not cause such problems (unless a miscompile). I dont see an obvious reason in valgrind either. Hmm, needs debugging. Christian |
|
From: Mark W. <mj...@re...> - 2012-10-18 08:41:25
|
On Thu, 2012-10-18 at 10:31 +0200, Christian Borntraeger wrote:
> Interesting, something on this box made valgrinds scheduler go wild.
>
> On programs doing fork we see
>
> +valgrind: m_scheduler/scheduler.c:545 (sched_fork_cleanup): Assertion 'VG_(running_tid) == me' failed.
>
> or
>
> +valgrind: m_syswrap/syswrap-main.c:1633 (vgPlain_client_syscall): Assertion 'VG_(is_running_thread)(tid)' failed.
>
> There are some modified versions of gcc/glibc etc from our toolchain folks, but it should
> not cause such problems (unless a miscompile).
>
> I dont see an obvious reason in valgrind either. Hmm, needs debugging.
Try reverting Revision: 13052
Log:
Fix 308341 vgdb should report process exit (or fatal signal)
patch from Mark Wielaard.
(with small modifications).
Also clarified some comments related to the resume reply.
That might not be it. But it might be that I got something wrong in the
gdbserver shutdown and the dying process accidentally tries to resurrect
the vgdb connection instead of tearing it down. I had that problem in my
first attempt of this patch, but thought I properly handled it. Maybe
not.
Cheers,
Mark
|
|
From: Christian B. <bor...@de...> - 2012-10-18 09:09:46
|
On 18/10/12 10:41, Mark Wielaard wrote: > > Try reverting Revision: 13052 > > Log: > Fix 308341 vgdb should report process exit (or fatal signal) > patch from Mark Wielaard. > (with small modifications). > Also clarified some comments related to the resume reply. > > That might not be it. But it might be that I got something wrong in the > gdbserver shutdown and the dying process accidentally tries to resurrect > the vgdb connection instead of tearing it down. I had that problem in my > first attempt of this patch, but thought I properly handled it. Maybe > not. No, its not the culprit. |