This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume
- From: Andreas Arnez <arnez at linux dot vnet dot ibm dot com>
- To: Yao Qi <qiyaoltc at gmail dot com>
- Cc: Sergio Durigan Junior <sergiodj at redhat dot com>, Pedro Alves <palves at redhat dot com>, GDB Patches <gdb-patches at sourceware dot org>, David Edelsohn <dje dot gcc at gmail dot com>, Edjunior Machado <emachado at redhat dot com>
- Date: Mon, 15 Jan 2018 16:22:23 +0100
- Subject: Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume
- Authentication-results: sourceware.org; auth=none
- References: <m3fu7dtzy8.fsf@oc1027705133.ibm.com> <7eccd434-6f47-590e-e53f-32076e99c98b@redhat.com> <m31sir5gik.fsf@oc1027705133.ibm.com> <CAH=s-POSOGChGGzM-iwTceSS8vw8cZbibdWnT2smk-kM32K=Cw@mail.gmail.com>
On Mon, Jan 15 2018, Yao Qi wrote:
> On Mon, Jan 15, 2018 at 2:43 PM, Andreas Arnez <arnez@linux.vnet.ibm.com> wrote:
>>
>> Sergio, now that this is in, we should be able to re-activate the
>> reporting for the s390 (and Power) Buildbots, right?
>>
>
> I am not sure ppc64 issue is resolved. See
> https://sourceware.org/ml/gdb-patches/2017-12/msg00414.html
> Note that I had a patch to fix fails in
> gdb.threads/process-dies-while-handling-bp.exp
> in this thread, but the tests with gdbserver still hang in some watchpoint
> tests.
Hm, too bad. Well, since this type of hang doesn't seem to occur on
s390, we can at least try re-activating s390 then.
--
Andreas