public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "glider at google dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/55599] switch from mach_override to mac interpose function support in libasan broke -static-libasan Date: Wed, 05 Dec 2012 04:51:00 -0000 [thread overview] Message-ID: <bug-55599-4-6YUOL8Rqkm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55599-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55599 --- Comment #5 from Alexander Potapenko <glider at google dot com> 2012-12-05 04:50:43 UTC --- The dynamic interposition library is based on the __DATA,__interpose dyld feature (see http://toves.freeshell.org/interpose/ or Amit Singh's "Mac OS X Internals" book), which strictly requires the interposing functions to be in a shared library that must be preloaded using DYLD_INSERT_LIBRARIES (ASan does that automatically in __asan_init) The dynamic library doesn't require the mach_override code (we don't link it in LLVM), but the static one does. Since you have removed the mach_override code, it's time to drop the static library support (note that in LLVM the static runtime library is still the default one, because it's now the one that simply works)
next prev parent reply other threads:[~2012-12-05 4:51 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-05 0:01 [Bug sanitizer/55599] New: " howarth at nitro dot med.uc.edu 2012-12-05 0:07 ` [Bug sanitizer/55599] " howarth at nitro dot med.uc.edu 2012-12-05 1:07 ` glider at google dot com 2012-12-05 3:47 ` howarth at nitro dot med.uc.edu 2012-12-05 4:01 ` kcc at gcc dot gnu.org 2012-12-05 4:51 ` glider at google dot com [this message] 2012-12-05 6:11 ` kcc at gcc dot gnu.org 2012-12-08 19:06 ` howarth at nitro dot med.uc.edu
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-55599-4-6YUOL8Rqkm@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).