From: Florian Weimer <fweimer@redhat.com>
To: Caroline Tice <cmtice@google.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Vtable pointer verification, gcc changes (patch 2 of 2)
Date: Thu, 08 Nov 2012 09:36:00 -0000 [thread overview]
Message-ID: <509B7D24.5040201@redhat.com> (raw)
In-Reply-To: <CABtf2+SdU_aWMj-v6J=WM8onenUX0UZY72bdKj2a4JEtUXe-pw@mail.gmail.com>
On 11/05/2012 06:48 PM, Caroline Tice wrote:
> As requested, I have split the original patch into two parts: GCC
> changes and runtime library changes. The attached patch is fore the
> gcc changes.
Out of curiosity, what's the primary source of wrong vtable values you
expect? User-after-free issues, heap spraying, or something else?
--
Florian Weimer / Red Hat Product Security Team
next prev parent reply other threads:[~2012-11-08 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 17:49 Caroline Tice
2012-11-07 16:58 ` Xinliang David Li
2012-11-16 18:21 ` Caroline Tice
[not found] ` <CABtf2+SnpddRF9kHsY-CyxNbS+3iQrUM7dqtZmbGJMNkS_WvBw@mail.gmail.com>
2012-11-28 16:17 ` Fwd: " Diego Novillo
2012-11-29 18:34 ` Jason Merrill
2012-11-29 18:35 ` Jason Merrill
2012-11-08 9:36 ` Florian Weimer [this message]
2012-11-08 16:56 ` Caroline Tice
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=509B7D24.5040201@redhat.com \
--to=fweimer@redhat.com \
--cc=cmtice@google.com \
--cc=gcc-patches@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).