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: Tue, 16 Jan 2018 09:12:00 -0000 [thread overview]
Message-ID: <86o9luf9r5.fsf@gmail.com> (raw)
In-Reply-To: <86o9mu8v32.fsf@gmail.com> (Yao Qi's message of "Tue, 19 Dec 2017 17:51:29 +0000")
Yao Qi <qiyaoltc@gmail.com> writes:
> As described in PR 18749, GDB/GDBserver may get an error on accessing
> memory or register because the thread may disappear. However, some
> path doesn't expect the error. This patch fixes this problem by
> marking the register unavailable when PTRACE_PEEKUSER fails instead
> of throwing error.
>
> gdb/gdbserver:
>
> 2017-12-19 Yao Qi <yao.qi@linaro.org>
>
> PR gdb/18749
> * linux-low.c (fetch_register): Call supply_register instead of
> error.
I pushed it in to master.
--
Yao (齐尧)
prev parent reply other threads:[~2018-01-16 9:12 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
2018-01-16 9:12 ` Yao Qi [this message]
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=86o9luf9r5.fsf@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