|
From: Rich C. <rc...@wi...> - 2016-09-18 13:50:39
|
On Sat, 17 Sep 2016 10:52:01 +0200
Philippe Waroquiers <phi...@sk...> wrote:
> On Fri, 2016-09-16 at 22:34 -0500, Rich Coe wrote:
> > Any tips or suggestions for debugging the issue?
> > Below is some data on the first hung test.
> The stacktrace shows that Valgrind gdbserver is waiting from
> some input from gdb, at the very beginning of execution.
> In the list of processes, I however do not see any gdb running.
> So, maybe you will see something wrong in the gdb output files
> (You should have this in the files
> gdbserver_tests/mcblocklistsearch.stdoutB.out
> and stderrB.out).
Thanks Philippe, that helped a lot.
>From these messages in the output file
> no --pid= arg given and multiple valgrind pids found:
> use --pid=24697 for cscope -d
> use --pid=15216 for /opt/google/chrome/chrome [...]
I found vgdb was looking for named pipe files in the gdbserver directory.
There were 200 or so of named pipe files there. I cleaned them out and
all the tests are running now.
I found the helgrind and drd tests bar_bad are hanging:
#0 vgModuleLocal_do_syscall_for_client_WRK () at m_syswrap/syscall-amd64-linux.S:173
#1 0x00000000380c0638 in do_syscall_for_client (syscall_mask=0x802c53d80, tst=0x802018f90, syscallno=202)
at m_syswrap/syswrap-main.c:339
#2 vgPlain_client_syscall (tid=tid@entry=1, trc=trc@entry=73) at m_syswrap/syswrap-main.c:2007
#3 0x00000000380bd02b in handle_syscall (tid=tid@entry=1, trc=73) at m_scheduler/scheduler.c:1118
#4 0x00000000380be697 in vgPlain_scheduler (tid=tid@entry=1) at m_scheduler/scheduler.c:1435
#5 0x00000000380cdc07 in thread_wrapper (tidW=1) at m_syswrap/syswrap-linux.c:103
#6 run_a_thread_NORETURN (tidW=1) at m_syswrap/syswrap-linux.c:156
#7 0x0000000000000000 in ?? ()
x/i
=> 0x381257ac <vgModuleLocal_do_syscall_for_client_WRK+89>: pop %r8
I'm not sure yet why this is hanging on this instruction. I'll have to
investigate further.
Rich
--
Rich Coe rc...@wi...
|