From: Luis Machado <luis.machado@arm.com>
To: Tom Tromey <tom@tromey.com>,
Luis Machado via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] [gdb/aarch64] Use safer memory read routines
Date: Thu, 10 Nov 2022 00:47:10 +0000 [thread overview]
Message-ID: <f7f12f21-27eb-ac59-4e6f-8de928417d87@arm.com> (raw)
In-Reply-To: <87iljp5qls.fsf@tromey.com>
Hi Tom,
On 11/8/22 16:59, Tom Tromey wrote:
>>>>>> "Luis" == Luis Machado via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Luis> PR 28796: GDB locks up after stopping on a breakpoint in invalidated memory
> Luis> on aarch64
>
> If you write "PR tdep/28796" instead, the commit will show up in
> bugzilla as well.
Indeed. I keep forgetting about that pattern.
>
> Also we've adopted the convention of adding a "Bug:" trailer with the
> full URL, though at present this doesn't really do anything.
>
> I think this is ok with these minor tweaks.
Fixed now and pushed.
>
> Tom
prev parent reply other threads:[~2022-11-10 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 7:14 Luis Machado
2022-11-08 16:59 ` Tom Tromey
2022-11-10 0:47 ` Luis Machado [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=f7f12f21-27eb-ac59-4e6f-8de928417d87@arm.com \
--to=luis.machado@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).