public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: "Willgerodt, Felix via Gdb-patches" <gdb-patches@sourceware.org>
Cc: "Willgerodt, Felix" <felix.willgerodt@intel.com>
Subject: Re: [PATCH 1/1] gdbserver, linux-low: add a couple of nullptr assertions.
Date: Tue, 29 Aug 2023 09:41:55 -0600	[thread overview]
Message-ID: <87ledtsvng.fsf@tromey.com> (raw)
In-Reply-To: <20230829134822.157625-1-felix.willgerodt@intel.com> (Felix via Gdb-patches Willgerodt's message of "Tue, 29 Aug 2023 13:48:22 +0000")

>>>>> Willgerodt, Felix via Gdb-patches <gdb-patches@sourceware.org> writes:

> This safeguards a couple of places that may theoretically return NULL but
> must not in this specific context.  These were found by a static analysis tool.

Seems fine to me.
Approved-By: Tom Tromey <tom@tromey.com>

Tom

  reply	other threads:[~2023-08-29 15:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-29 13:48 Willgerodt, Felix
2023-08-29 15:41 ` Tom Tromey [this message]
2023-08-30  6:40   ` Willgerodt, Felix

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=87ledtsvng.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=felix.willgerodt@intel.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).