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/58937] Preloaded libasan segfaults on unsanitized executables
Date: Mon, 07 Apr 2014 15:10:00 -0000	[thread overview]
Message-ID: <bug-58937-4-iXfEmIe4Nb@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 #17 from Yury Gribov <y.gribov at samsung dot com> ---
This should be fully resolved once
https://github.com/llvm-mirror/compiler-rt/commit/d6535ea4c4d49078a93735b315b8518fb692a592
is merged into gcc trunk.

BTW it no longer reproduces on trunk because newer versions of libstdc++
silently call __asan_init from __cxa_atexit in some constructor:
 #1  0x00007ffff6f45a09 in __asan::InitializeAsanInterceptors() () at
/home/ygribov/src/gcc-master/libsanitizer/asan/asan_interceptors.cc:710
 #2  0x00007ffff6f5b71f in __asan_init_v3 () from
/home/ygribov/install/gcc-master/lib64/libasan.so
 #3  0x00007ffff6f24462 in __interceptor___cxa_atexit () at
/home/ygribov/src/gcc-master/libsanitizer/asan/asan_interceptors.cc:671
 #4  0x00007ffff62bfa32 in std::future_category() () at
/home/ygribov/src/gcc-master/libstdc++-v3/src/c++11/future.cc:63
 #5  0x00007ffff6265c79 in _GLOBAL__sub_I_compatibility_thread_c__0x.cc () at
/home/ygribov/src/gcc-master/libstdc++-v3/src/c++11/compatibility-thread-c++0x.cc:49
 #6  0x00007ffff7de9306 in call_init (l=<optimized out>, argc=1,
argv=0x7fffffffdeb8, env=0x7fffffffdec8) at dl-init.c:85
 #7  0x00007ffff7de93df in call_init (env=<optimized out>, argv=<optimized
out>, argc=<optimized out>, l=<optimized out>) at dl-init.c:52
 #8  _dl_init (main_map=0x7ffff7ffe2c8, argc=1, argv=0x7fffffffdeb8,
env=0x7fffffffdec8) at dl-init.c:134
 #9  0x00007ffff7ddb6ea in _dl_start_user () from /lib64/ld-linux-x86-64.so.2


  parent reply	other threads:[~2014-04-07 15:10 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
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 [this message]
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-iXfEmIe4Nb@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).