public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "konstantin.s.serebryany at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/55379] -static -static-libasan pass -Bdynamic to linker
Date: Sun, 18 Nov 2012 18:58:00 -0000 [thread overview]
Message-ID: <bug-55379-4-ul5AjYMaJd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55379-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55379
Konstantin Serebryany <konstantin.s.serebryany at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |konstantin.s.serebryany at
| |gmail dot com
--- Comment #3 from Konstantin Serebryany <konstantin.s.serebryany at gmail dot com> 2012-11-18 18:58:00 UTC ---
Note: fully static linking is not supported by libsanitizer at all and I don't
think it will.
Reason: on linux asan uses "dlsym(RTLD_NEXT, ...)" and on Mac it uses
(will soon use) function inerposition.
Neither works for fully static binaries, afaict.
next prev parent reply other threads:[~2012-11-18 18:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 14:51 [Bug driver/55379] New: -static -static-libasan doesn't create static binary hjl.tools at gmail dot com
2012-11-18 14:52 ` [Bug driver/55379] " hjl.tools at gmail dot com
2012-11-18 14:56 ` [Bug driver/55379] -static -static-libasan pass -Bdynamic to linker hjl.tools at gmail dot com
2012-11-18 18:58 ` konstantin.s.serebryany at gmail dot com [this message]
2012-11-18 19:35 ` hjl.tools at gmail dot com
2012-11-22 11:14 ` [Bug sanitizer/55379] " jakub at gcc dot gnu.org
2012-11-22 11:31 ` jakub at gcc dot gnu.org
2012-11-22 15:17 ` hjl at gcc dot gnu.org
2012-11-22 15:18 ` hjl.tools at gmail dot com
2012-11-22 15:19 ` hjl.tools at gmail dot com
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-55379-4-ul5AjYMaJd@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: 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).