Re: ppc64* native-gdbserver testsuite hangs on gdb.threads/process-dies-while-handling-bp.exp

[Yao Qi <qiyaoltc@gmail.com>]

On Tue, Dec 19, 2017 at 9:17 AM, Edjunior Machado <edjunior@gmail.com> wrote:
> from the discussions that followed
> https://sourceware.org/ml/gdb-patches/2017-12/msg00374.html, regarding
> buildings that were taking much longer than the expected, noticed that
> gdb.threads/process-dies-while-handling-bp.exp is hanging on ppc64[le] when
> testing native-gdbserver, leading the testrun to take hours until it is
> timed out. According to git bisect, it seems it started to happen after
> this commit:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;a=commit;h=173981
>
> However, I couldn't figure out what exactly might be root cause of this
> behavior. Also, the same doesn't happen on default (non-gdbserver)
> testsuite run. Any idea/suggestion?
>

It is a known issue in GDB, described in PR 18749, rather than a
regression, so git bisect can't tell you anything useful.  Pedro fixed
one GDBserver crash caused by 18749, but PR 18749 is still
there.

I can reproduce the timeout on gcc110,

KFAIL: gdb.threads/process-dies-while-handling-bp.exp: non_stop=on:
cond_bp_target=0: inferior 1 exited (timeout) (PRMS: gdb/18749)
Remote debugging from host 127.0.0.1^M
gdbserver: reading register 10: No such process^M
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Killing process(es): 15614^M
monitor exit^M
Ignoring packet error, continuing...

I think some code path in GDBserver doesn't expect this error.

-- 
Yao (齐尧)