From: Jonathan Wakely <jwakely@redhat.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org,
"François Dumont" <frs.dumont@gmail.com>
Subject: Re: [patch] Enable lightweight checks with _GLIBCXX_ASSERTIONS.
Date: Mon, 07 Sep 2015 20:10:00 -0000 [thread overview]
Message-ID: <20150907195939.GT2631@redhat.com> (raw)
In-Reply-To: <87r3mauiud.fsf@mid.deneb.enyo.de>
On 07/09/15 21:31 +0200, Florian Weimer wrote:
>* Jonathan Wakely:
>
>> This patch adds the "debug mode lite" we've been talking about, by
>> changing __glibcxx_assert to be activated by _GLIBCXX_ASSERTIONS
>> instead of _GLIBCXX_DEBUG (and making the latter imply the former).
>
>Interesting. Is this mode ABI-compatible with the default mode?
Yes, that's the main reason I want to make this change.
>Should _FORTIFY_SOURCE imply _GLIBCXX_ASSERTIONS?
Yes, I think it should.
You can read my notes on these "debug mode lite" checks at
https://gcc.gnu.org/wiki/LibstdcxxDebugMode (including "This should be
discussed with Glibc and security teams" and I specifically had you in
mind when I wrote that :-)
Your thoughts would be much appreciated, especially regarding
_FORTIFY_SOURCE and which kind of new checks you think would be
appropriate to add.
next prev parent reply other threads:[~2015-09-07 19:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 19:04 Jonathan Wakely
2015-09-07 19:14 ` Daniel Krügler
2015-09-07 19:59 ` Jonathan Wakely
2015-09-07 20:12 ` Jonathan Wakely
2015-09-07 20:20 ` Daniel Krügler
2015-09-07 19:53 ` Florian Weimer
2015-09-07 20:10 ` Jonathan Wakely [this message]
2015-09-08 13:15 ` Michael Matz
2015-09-08 14:47 ` Jonathan Wakely
2015-09-08 15:03 ` Florian Weimer
2015-09-08 15:50 ` Jonathan Wakely
2015-09-09 16:18 ` Florian Weimer
2015-09-10 16:38 ` Martin Sebor
2015-09-10 16:39 ` Florian Weimer
2015-09-10 17:08 ` Martin Sebor
2015-09-14 10:11 ` Florian Weimer
2015-09-26 22:02 ` Jonathan Wakely
2015-09-26 22:11 ` Florian Weimer
2015-09-27 15:14 ` Jonathan Wakely
2015-09-28 14:54 ` Florian Weimer
2015-09-08 20:01 ` François Dumont
2015-09-09 14:03 ` Jonathan Wakely
2015-09-09 17:48 ` Jonathan Wakely
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=20150907195939.GT2631@redhat.com \
--to=jwakely@redhat.com \
--cc=frs.dumont@gmail.com \
--cc=fw@deneb.enyo.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).