[Bug server/30387] gdbserver assert error on arm platform

["kevinb at redhat dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=30387

--- Comment #22 from Kevin Buettner <kevinb at redhat dot com> ---
(In reply to Luis Machado from comment #21)

Hi Luis,

Regarding the length of time that it takes to run this test case: 
I've seen some instances where it took in excess of 100 iterations to
observe the software single-step related failure.  The number of
iterations is currently set to 200, but we might drop it to 150, which
should decrease the time needed to run the test by about 25%.  We
could also eliminate one or more of the outer loops, but this would
decrease coverage of (e.g.) the target-non-stop=on case.  Doing so,
however, would likely eliminate the (other) failures that you've
observed.

Regarding whether or not to run the test for native targets: It
is true that this test was written after finding a bug in the software
single-step related code in gdbserver.  However, it seems to me that
it'd be possible to introduce code causing buggy behavior for native
gdb, whether it requires software single-step or not.  Therefore, I'd
prefer to run it for all targets.

Regarding unexpected failures for a patched gdbserver:  I see these
too, and do not know why they occur.  I've only seen them for the
"target-non-stop=on" case(s), and they do seem to be somewhat racy in
nature.  I recall one test run where there were no failures, but I
usually see 2 when testing on a Raspberry Pi.  I think it's likely
that there's another bug that needs fixing.  We could setup a KFAIL
for that particular case.  Or, if we were to eliminate testing
target-non-stop=on, those failures would also go away.  (I didn't
set up a KFAIL for it because leaving them as FAIL means that someone
is more likely to try to fix the bug...)

-- 
You are receiving this mail because:
You are on the CC list for the bug.