public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Gary Benson <gbenson@redhat.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Use volatile pointers when attempting to trigger SIGSEGVs
Date: Mon, 13 Jul 2020 14:50:00 +0100	[thread overview]
Message-ID: <20200713135000.GB17938@blade.nx> (raw)
In-Reply-To: <3a5c3aa5-2ff3-7246-5966-e296265859f1@palves.net>

Pedro Alves wrote:
> On 6/30/20 2:42 PM, Gary Benson via Gdb-patches wrote:
> > Hi all,
> > 
> > Clang fails to compile a number of files with the following warning:
> > indirection of non-volatile null pointer will be deleted, not trap
> > [-Wnull-dereference].  This patch qualifies the relevant pointers
> > with 'volatile'.
> > 
> > Checked on Fedora 31 x86_64, GCC and clang.  Ok to commit?
> 
> OK

Thanks, I've pushed it.

Cheers,
Gary

-- 
Gary Benson - he / him / his
Principal Software Engineer, Red Hat


      reply	other threads:[~2020-07-13 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30 13:42 Gary Benson
2020-07-10 14:39 ` Pedro Alves
2020-07-13 13:50   ` Gary Benson [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=20200713135000.GB17938@blade.nx \
    --to=gbenson@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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).