From: Edjunior Machado <edjunior@gmail.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: ppc64* native-gdbserver testsuite hangs on gdb.threads/process-dies-while-handling-bp.exp
Date: Thu, 21 Dec 2017 16:02:00 -0000 [thread overview]
Message-ID: <CAJJrRvYk7PEqn7k-YQ+uSKxHiT7NPWH8L5taBCfDbfSQO98eZQ@mail.gmail.com> (raw)
In-Reply-To: <CAH=s-POmg=2tPfqC1=a4QzN4gxs-wJT7JkhQjTrkeKVndbxk8g@mail.gmail.com>
Hi Yao,
On Wed, Dec 20, 2017 at 10:35 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
> On Wed, Dec 20, 2017 at 4:23 PM, Yao Qi <qiyaoltc@gmail.com> wrote:
> > Is it gdb.base/watchpoints.exp? My regression test running on gcc110
> > is very slow, blocked by gdb.base/watchpoints.exp. The test needs two
> > HW watchpoints, but ppc only has one HW watchpoint register. GDB
> > native can do resource counting, so it is smart enough to switch to
> > SW wathcpoint if there is not enough HW watchpoint registers. However,
> > GDB remote can *not* do resource counting, so GDB fails to insert
> > watchpoints, and all the following tests timeout.
> >
>
exactly, gdb.base/watchpoints.exp is the hanging testcase now.
>
> Looks ppc64-linux gdbserver doesn't support watchpoint, so we need
> to improve test cases to probe hw watchpoint support. See
> test "set probe hw watchpoint" in watchpoint-stops-at-right-insn.exp.
>
Agreed, ppc64[le] gdbserver currently does not implement hw watchpoint
support; however, despite the high number of failures on the mentioned test
(and possibly others) because of that, from what I could git-bisect, it
didn't hang the native-gdbserver testrun until commit
c65d6b55b3a592906c470c566f57ad8ceacc1605.
Thanks and regards,
Edjunior
>
> --
> Yao (齐尧)
>
next prev parent reply other threads:[~2017-12-21 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 9:17 Edjunior Machado
2017-12-19 16:27 ` Yao Qi
2017-12-19 17:51 ` Yao Qi
2017-12-20 15:24 ` Edjunior Machado
2017-12-20 16:23 ` Yao Qi
2017-12-20 21:35 ` Yao Qi
2017-12-21 16:02 ` Edjunior Machado [this message]
2018-01-16 9:12 ` Yao Qi
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=CAJJrRvYk7PEqn7k-YQ+uSKxHiT7NPWH8L5taBCfDbfSQO98eZQ@mail.gmail.com \
--to=edjunior@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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