public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gschafer at zip dot com dot au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/14206] Mention that exec-shield-randomize (linux) conflicts with PCH Date: Wed, 20 Jul 2005 03:40:00 -0000 [thread overview] Message-ID: <20050720023146.24597.qmail@sourceware.org> (raw) In-Reply-To: <20040219050450.14206.giovannibajo@libero.it> ------- Additional Comments From gschafer at zip dot com dot au 2005-07-20 02:31 ------- Stock Linux kernel 2.6.12 introduced "address space randimization" which appears to be essentially the same thing as RH's exec-shield-randomize. More info about this issue here: http://gcc.gnu.org/ml/gcc/2005-07/msg00851.html -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14206
prev parent reply other threads:[~2005-07-20 2:31 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-02-19 5:05 [Bug web/14206] New: Mention that exec-shield " giovannibajo at libero dot it 2004-02-19 5:08 ` [Bug target/14206] " pinskia at gcc dot gnu dot org 2004-02-19 5:46 ` aoliva at gcc dot gnu dot org 2004-02-19 12:00 ` giovannibajo at libero dot it 2004-02-19 21:46 ` geoffk at geoffk dot org 2004-03-02 19:24 ` giovannibajo at libero dot it 2004-03-03 12:42 ` giovannibajo at libero dot it 2004-03-25 5:57 ` [Bug target/14206] Mention that exec-shield-randomize " ian at wasabisystems dot com 2004-03-27 3:37 ` cvs-commit at gcc dot gnu dot org 2004-03-27 3:39 ` ian at wasabisystems dot com 2004-03-27 13:39 ` giovannibajo at libero dot it 2004-03-29 16:39 ` ian at wasabisystems dot com 2004-03-29 16:42 ` pinskia at physics dot uc dot edu 2004-03-29 16:48 ` ian at wasabisystems dot com 2005-07-20 3:40 ` gschafer at zip dot com dot au [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=20050720023146.24597.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).