public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: libstdc++@gcc.gnu.org
Cc: Paul Pluzhnikov <ppluzhnikov@google.com>,
	dnovillo@google.com, gcc-patches@gcc.gnu.org
Subject: Re: [google gcc-4_7, integration] Scribble on destructed strings to catch invalid accesses.
Date: Fri, 25 Jan 2013 00:15:00 -0000	[thread overview]
Message-ID: <CAH6eHdSzFtveK1pNdMHY9yjCEva97Lo0LYpZQA+ccuV4s_RYEw@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1301241952370.3737@laptop-mg.saclay.inria.fr>

On 24 January 2013 19:03, Marc Glisse wrote:
> On Wed, 23 Jan 2013, Paul Pluzhnikov wrote:
>
>> This patch allows us to catch use of destructed strings.
>
>
> Hello,
>
> while a number of the google debug patches are just cheaper versions (that
> don't break the ABI) of what libstdc++'s debug mode provides, this
> overwriting of classes on destruction is not as obviously redundant, and I
> wonder whether something like it (done consistently for many classes) could
> go to trunk...

Thanks for pointing this out, Marc.

This does look like something that could be included in debug mode,
but probably not until we're back in Stage 1.  Please either put it in
Bugzilla (and CC me) or if you're diligent enough to remember please
email us again during Stage 1  :-)

Googlers, please include the libstdc++ list on patches to the
libstdc++ code, even if it's only to a google branch. I don't read
gcc-patches but am still interested in the changes you make to the
code on your branch.

  reply	other threads:[~2013-01-25  0:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24  6:23 Paul Pluzhnikov
2013-01-24 12:08 ` Diego Novillo
2013-01-24 19:03 ` Marc Glisse
2013-01-25  0:15   ` Jonathan Wakely [this message]
2013-01-25 13:49     ` Diego Novillo
2013-01-25 14:52     ` Paul Pluzhnikov

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=CAH6eHdSzFtveK1pNdMHY9yjCEva97Lo0LYpZQA+ccuV4s_RYEw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=dnovillo@google.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ppluzhnikov@google.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).