public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "y.gribov at samsung dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/64234] Statically sanitized executable does not export ASan symbols
Date: Tue, 09 Dec 2014 10:35:00 -0000 [thread overview]
Message-ID: <bug-64234-4-yxcts5mfqN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64234-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64234
--- Comment #4 from Yury Gribov <y.gribov at samsung dot com> ---
(In reply to Jakub Jelinek from comment #3)
> But why do you want to use -static-libasan ? Just link it dynamically...
For one thing it can speed up code by avoiding PLT calls.
> --dynamic-list is hard to maintain, aren't there hundreds of symbols that
> are exported from libasan?
Indeed there are, upstream has a special script to autogenerate file with
symbols.
next prev parent reply other threads:[~2014-12-09 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 9:35 [Bug sanitizer/64234] New: " y.gribov at samsung dot com
2014-12-09 10:02 ` [Bug sanitizer/64234] " jakub at gcc dot gnu.org
2014-12-09 10:18 ` y.gribov at samsung dot com
2014-12-09 10:22 ` jakub at gcc dot gnu.org
2014-12-09 10:35 ` y.gribov at samsung dot com [this message]
2022-05-31 8:36 ` mkh199740 at mail dot ru
2022-07-18 13:07 ` boris at kolpackov dot net
2022-11-12 2:55 ` mkh199740 at mail dot ru
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-64234-4-yxcts5mfqN@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).