From: Yao Qi <qiyaoltc@gmail.com>
To: Edjunior Machado <edjunior@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: Wed, 20 Dec 2017 16:23:00 -0000 [thread overview]
Message-ID: <CAH=s-PNe-YyzBAvowg5y3PgxVOh6kuPcHBuFN8x2qz5WeaRAUg@mail.gmail.com> (raw)
In-Reply-To: <CAJJrRvascRev5Q1mH=MzG=eT72fBiUhMQxEVcGsRVW1e=J9fDw@mail.gmail.com>
On Wed, Dec 20, 2017 at 3:23 PM, Edjunior Machado <edjunior@gmail.com> wrote:
> thanks a lot for the patch! Testing the fix on Fedora26, confirmed that
> native-gdbserver no longer hangs on
> gdb.threads/process-dies-while-handling-bp.exp in both ppc64le and be.
>
> Unfortunately, I couldn't regtest running the complete testsuite due to
> another hang I'm still checking (likely caused by hw watch not working
> properly on such boxes).
>
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.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-12-20 16:23 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 [this message]
2017-12-20 21:35 ` Yao Qi
2017-12-21 16:02 ` Edjunior Machado
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='CAH=s-PNe-YyzBAvowg5y3PgxVOh6kuPcHBuFN8x2qz5WeaRAUg@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=edjunior@gmail.com \
--cc=gdb-patches@sourceware.org \
/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