public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/18749] problems if whole process dies while (ptrace-) stopped
Date: Wed, 03 Jan 2024 14:49:44 +0000 [thread overview]
Message-ID: <bug-18749-4717-2CbcgH6V3d@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18749-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18749
Hannes Domani <ssbssa at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ssbssa at sourceware dot org
--- Comment #5 from Hannes Domani <ssbssa at sourceware dot org> ---
(In reply to Sourceware Commits from comment #4)
> The master branch has been updated by Yao Qi <qiyao@sourceware.org>:
>
> https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;
> h=9a70f35c8d872bb5542e98e34b8b044228dcb844
>
> commit 9a70f35c8d872bb5542e98e34b8b044228dcb844
> Author: Yao Qi <yao.qi@linaro.org>
> Date: Tue Jan 16 09:05:39 2018 +0000
>
> Mark register unavailable when PTRACE_PEEKUSER fails
>
> 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:
>
> 2018-01-16 Yao Qi <yao.qi@linaro.org>
>
> PR gdb/18749
> * linux-low.c (fetch_register): Call supply_register instead of
> error.
Can this be closed?
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-03 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 11:18 [Bug gdb/18749] New: " palves at redhat dot com
2015-07-31 11:18 ` [Bug gdb/18749] " palves at redhat dot com
2015-08-21 19:13 ` cvs-commit at gcc dot gnu.org
2024-01-03 14:49 ` ssbssa at sourceware dot org [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=bug-18749-4717-2CbcgH6V3d@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).