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/56393] SIGSEGV when -fsanitize=address and dynamic lib with global objects
Date: Tue, 15 Oct 2013 13:39:00 -0000 [thread overview]
Message-ID: <bug-56393-4-FRKAC9f8Ul@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56393-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56393
Yury Gribov <y.gribov at samsung dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |y.gribov at samsung dot com
--- Comment #27 from Yury Gribov <y.gribov at samsung dot com> ---
(In reply to Evgeniy Stepanov from comment #13)
> I don't see what can be done in that case. We should just declare it
> unsupported.
Evgeniy,
Do you think we can somehow detect this invalid usage at link/runtime and
inform user? Such invalid linkage tends to slip in in large SW projects with
have precompiled parts and causes complete mess at runtime.
-Y
next prev parent reply other threads:[~2013-10-15 13:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 13:02 [Bug sanitizer/56393] New: " t-gcc-bugzilla at snowelm dot com
2013-02-19 13:50 ` [Bug sanitizer/56393] " kcc at gcc dot gnu.org
2013-02-19 14:02 ` t-gcc-bugzilla at snowelm dot com
2013-02-19 14:11 ` kcc at gcc dot gnu.org
2013-02-19 15:23 ` t-gcc-bugzilla at snowelm dot com
2013-02-19 15:27 ` t-gcc-bugzilla at snowelm dot com
2013-02-19 18:34 ` kcc at gcc dot gnu.org
2013-02-19 20:38 ` eugeni.stepanov at gmail dot com
2013-02-20 14:30 ` kcc at gcc dot gnu.org
2013-02-20 14:43 ` jakub at gcc dot gnu.org
2013-02-20 14:50 ` kcc at gcc dot gnu.org
2013-02-20 14:57 ` eugeni.stepanov at gmail dot com
2013-02-20 15:03 ` jakub at gcc dot gnu.org
2013-02-20 18:30 ` eugeni.stepanov at gmail dot com
2013-02-21 10:54 ` amonakov at gcc dot gnu.org
2013-02-21 11:36 ` kcc at gcc dot gnu.org
2013-02-21 11:52 ` eugeni.stepanov at gmail dot com
2013-02-22 6:39 ` t-gcc-bugzilla at snowelm dot com
2013-02-22 6:56 ` pinskia at gcc dot gnu.org
2013-02-22 7:02 ` kcc at gcc dot gnu.org
2013-02-22 9:02 ` t-gcc-bugzilla at snowelm dot com
2013-02-22 16:08 ` jakub at gcc dot gnu.org
2013-04-07 8:44 ` david.abdurachmanov at gmail dot com
2013-04-08 6:32 ` kcc at gcc dot gnu.org
2013-04-08 6:56 ` jakub at gcc dot gnu.org
2013-06-01 21:35 ` david.abdurachmanov at gmail dot com
2013-06-03 7:56 ` kcc at gcc dot gnu.org
2013-10-15 13:39 ` y.gribov at samsung dot com [this message]
2013-10-15 13:54 ` eugeni.stepanov at gmail dot com
2013-10-15 14:02 ` pluto at agmk dot net
2013-10-15 14:04 ` eugeni.stepanov at gmail dot com
2013-10-15 17:43 ` tetra2005 at gmail dot com
2013-10-15 17:45 ` tetra2005 at gmail dot com
2013-10-15 17:52 ` eugeni.stepanov at gmail dot com
2013-10-15 18:04 ` tetra2005 at gmail dot com
2013-10-16 12:05 ` y.gribov at samsung dot com
2013-10-16 13:29 ` y.gribov at samsung dot com
2013-10-16 13:44 ` eugeni.stepanov at gmail dot com
2013-10-16 14:02 ` y.gribov at samsung dot com
2013-10-30 7:53 ` jakub at gcc dot gnu.org
2013-10-30 8:12 ` y.gribov at samsung dot com
2013-10-30 8:14 ` y.gribov at samsung dot com
2013-10-30 8:23 ` jakub at gcc dot gnu.org
2013-10-30 9:38 ` y.gribov at samsung dot com
2014-09-30 8:36 ` 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-56393-4-FRKAC9f8Ul@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).