From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tromey@adacore.com>
Subject: Re: [PATCH] Use scoped_value_mark in two more places
Date: Fri, 09 Jun 2023 07:42:25 -0600 [thread overview]
Message-ID: <871qikah1a.fsf@tromey.com> (raw)
In-Reply-To: <20230525125737.1849340-1-tromey@adacore.com> (Tom Tromey via Gdb-patches's message of "Thu, 25 May 2023 06:57:37 -0600")
>>>>> "Tom" == Tom Tromey via Gdb-patches <gdb-patches@sourceware.org> writes:
Tom> I found a couple of spots that could use scoped_value_mark. One of
Tom> them is a spot that didn't consider the possibility that value_mark
Tom> can return NULL. I tend to doubt this can be seen in this context,
Tom> but nevertheless this is safer.
Tom> Regression tested on x86-64 Fedora 36.
I'm checking this in.
Tom
prev parent reply other threads:[~2023-06-09 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 12:57 Tom Tromey
2023-06-09 13:42 ` Tom Tromey [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=871qikah1a.fsf@tromey.com \
--to=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).