public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eugeni.stepanov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/58937] Preloaded libasan segfaults on unsanitized executables
Date: Tue, 12 Nov 2013 08:52:00 -0000	[thread overview]
Message-ID: <bug-58937-4-UBZiXRsE4O@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58937-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58937

--- Comment #8 from Evgeniy Stepanov <eugeni.stepanov at gmail dot com> ---
I'm a little surprised we did not run into this on Android yet - we use the
same LD_PRELOAD scheme there. Are you linking libasan with libpthread? This
might go away as libpthread constructors call one of the ASan interceptors that
does ENSURE_ASAN_INITED(). Arguably, all interceptors should do it.

I think Kostya raises valid points, but still, adding attribute((constructor))
is reasonable.


  parent reply	other threads:[~2013-11-12  8:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-31 10:25 [Bug sanitizer/58937] New: " y.gribov at samsung dot com
2013-10-31 11:37 ` [Bug sanitizer/58937] " y.gribov at samsung dot com
2013-10-31 11:39 ` jakub at gcc dot gnu.org
2013-10-31 12:23 ` y.gribov at samsung dot com
2013-11-11 15:06 ` y.gribov at samsung dot com
2013-11-12  8:01 ` samsonov at google dot com
2013-11-12  8:16 ` kcc at gcc dot gnu.org
2013-11-12  8:45 ` y.gribov at samsung dot com
2013-11-12  8:52 ` eugeni.stepanov at gmail dot com [this message]
2013-11-13  8:49 ` y.gribov at samsung dot com
2013-11-13  9:53 ` eugeni.stepanov at gmail dot com
2013-11-14 10:48 ` y.gribov at samsung dot com
2013-11-14 10:50 ` y.gribov at samsung dot com
2013-11-15  8:53 ` eugeni.stepanov at gmail dot com
2014-01-22  6:37 ` y.gribov at samsung dot com
2014-01-23  7:54 ` y.gribov at samsung dot com
2014-04-07 15:10 ` y.gribov at samsung dot com
2014-08-28 14:44 ` y.gribov at samsung 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-58937-4-UBZiXRsE4O@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).