From: Andreas Arnez <arnez@linux.vnet.ibm.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Sergio Durigan Junior <sergiodj@redhat.com>,
Pedro Alves <palves@redhat.com>,
GDB Patches <gdb-patches@sourceware.org>,
David Edelsohn <dje.gcc@gmail.com>,
Edjunior Machado <emachado@redhat.com>
Subject: Re: [pushed + testcase] Re: [PATCH] Fix GDB hang with remote after error from resume
Date: Mon, 15 Jan 2018 15:22:00 -0000 [thread overview]
Message-ID: <m3wp0j405s.fsf@oc1027705133.ibm.com> (raw)
In-Reply-To: <CAH=s-POSOGChGGzM-iwTceSS8vw8cZbibdWnT2smk-kM32K=Cw@mail.gmail.com> (Yao Qi's message of "Mon, 15 Jan 2018 14:52:56 +0000")
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
next prev parent reply other threads:[~2018-01-15 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 16:56 Andreas Arnez
2018-01-12 19:11 ` [pushed + testcase] " Pedro Alves
2018-01-15 14:43 ` Andreas Arnez
2018-01-15 14:53 ` Yao Qi
2018-01-15 15:22 ` Andreas Arnez [this message]
2018-01-15 16:10 ` Yao Qi
2018-01-15 17:37 ` Edjunior Machado
2018-01-15 18:17 ` Pedro Alves
2018-01-15 20:11 ` Sergio Durigan Junior
2018-01-15 15:18 ` Sergio Durigan Junior
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3wp0j405s.fsf@oc1027705133.ibm.com \
--to=arnez@linux.vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=emachado@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
--cc=qiyaoltc@gmail.com \
--cc=sergiodj@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox