On Thu, 2015-02-12 at 15:33 -0800, Mark Roberts wrote:
> I’m in the process of upgrading from Vulcan 3.9 to 3.10.1. I’m having
> trouble with the new test gdbserver_tests/nlvgdbsigqueue.vgtest. It
> looks like it is not getting the gdb signal as it will run to timeout
> (which is a loooong time). All the other gdbserver tests run fine as
> do all the rest of the tests for that matter.
>
>
>
> Running:
>
> Linux version 3.16.3-200.fc20.x86_64
> (moc...@bk...) (gcc version 4.8.3
> 20140624 (Red Hat 4.8.3-1) (GCC) ) #1 SMP Wed Sep 17 22:34:21 UTC 2014
>
>
>
> Any thoughts?
No idea.
It runs ok on a bunch of platforms.
This test is somewhat sensitive to timing
(i.e. we have some sleep here and there that are supposed
to synchronise the events). So, the test might fail maybe due
to a highly loaded system ?
Can you run the test with more trace ?
E.g. run with
export EXTRA_REGTEST_OPTS="-v -v -v -d -d -d"
to have tracing at valgrind side,
and add
-d -d 2>vgdb.stderr.out
at the end of the target remote | ...
line in nlvgdbsigqueue.stdinB.gdb
then do
perl tests/vg_regtest --keep-unfiltered gdbserver_tests/nlvgdbsigqueue
The resulting trace files might help to understand what is going wrong.
Philippe
|
