public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug boehm-gc/52179] New: boehm-gc incompatible with aslr on darwin11 Date: Wed, 08 Feb 2012 23:47:00 -0000 [thread overview] Message-ID: <bug-52179-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52179 Bug #: 52179 Summary: boehm-gc incompatible with aslr on darwin11 Classification: Unclassified Product: gcc Version: 4.7.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: boehm-gc AssignedTo: unassigned@gcc.gnu.org ReportedBy: howarth@nitro.med.uc.edu Currently we see the failures... FAIL: boehm-gc.c/gctest.c -O2 execution test FAIL: boehm-gc.c/leak_test.c -O2 execution test FAIL: boehm-gc.c/thread_leak_test.c -O2 execution test FAIL: boehm-gc.lib/staticrootstest.c -O2 execution test at -m32/-m64 on x86_64-apple-darwin11. Interestingly, if boehm-gc/testsuite/lib/boehm-gc.exp is adjusted pass -Wl,-pie to these tests, the failures are not seen under aslr on x86_64-apple-darwin10. This is the same behavior seen for PR52042 which suggests that the issue and fix may be similar. Perhaps the same approach used in could be applied to boehm-gc/dyn_load.c.
next reply other threads:[~2012-02-08 23:47 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-08 23:47 howarth at nitro dot med.uc.edu [this message] 2012-02-08 23:55 ` [Bug boehm-gc/52179] " howarth at nitro dot med.uc.edu 2012-02-09 0:35 ` howarth at nitro dot med.uc.edu 2012-02-09 0:40 ` howarth at nitro dot med.uc.edu 2012-02-09 0:47 ` howarth at nitro dot med.uc.edu 2012-02-09 0:57 ` howarth at nitro dot med.uc.edu 2012-02-09 15:06 ` howarth at nitro dot med.uc.edu 2012-02-11 1:11 ` howarth at nitro dot med.uc.edu 2012-02-22 22:32 ` patrick.marlier at gmail dot com 2012-02-23 4:34 ` howarth at nitro dot med.uc.edu 2012-02-23 4:40 ` mikestump at comcast dot net 2012-02-23 8:19 ` mikestump at comcast dot net 2012-02-23 15:17 ` howarth at nitro dot med.uc.edu 2012-02-23 15:18 ` iains at gcc dot gnu.org 2012-02-23 15:42 ` patrick.marlier at gmail dot com 2012-02-23 15:50 ` patrick.marlier at gmail dot com 2012-02-23 15:53 ` howarth at nitro dot med.uc.edu 2012-02-23 18:31 ` howarth at nitro dot med.uc.edu 2012-02-23 18:38 ` howarth at nitro dot med.uc.edu 2012-02-23 18:44 ` howarth at nitro dot med.uc.edu 2012-02-23 18:51 ` mikestump at comcast dot net 2012-02-23 18:53 ` howarth at nitro dot med.uc.edu 2012-02-23 18:57 ` patrick.marlier at gmail dot com 2012-02-23 18:58 ` mikestump at comcast dot net 2012-02-23 21:02 ` howarth at nitro dot med.uc.edu 2012-02-23 21:57 ` mikestump at comcast dot net 2012-02-23 22:05 ` howarth at nitro dot med.uc.edu 2012-02-24 15:52 ` pmarlier at gcc dot gnu.org 2012-02-29 6:04 ` howarth at nitro dot med.uc.edu 2012-03-02 18:23 ` mrs at gcc dot gnu.org 2012-03-02 18:35 ` mrs at gcc dot gnu.org
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=bug-52179-4@http.gcc.gnu.org/bugzilla/ \ --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).