public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/99179] asan failures with -Os on x86_64-apple-darwin20
Date: Wed, 17 Mar 2021 19:24:05 +0000	[thread overview]
Message-ID: <bug-99179-4-LJqDH2480T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99179-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99179

--- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> ---
I did some more checking on this.

1) It seems that something we produce in the unwind info for alloca is not
compatible with atos.

2) The objects all pass "dwarfdump --verify"

3) If I run the objects under lldb, breakpoints set by line number seem to work
properly.

4) If I use a recent llvm-symbolizer (ASAN_SYMBOLIZER_PATH=) the tests work.

5) the tests also work with clang / libsanitizer.

so, perhaps we have some subtle problem with the unwind information we produce
with -Os (and when there's an alloca or stack adjustment) - but I don't see
this as something I can address for GCC11 (even if it's fixable).

  parent reply	other threads:[~2021-03-17 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-20 13:27 [Bug sanitizer/99179] New: " dominiq at lps dot ens.fr
2021-02-20 20:25 ` [Bug sanitizer/99179] " iains at gcc dot gnu.org
2021-03-17 19:24 ` iains at gcc dot gnu.org [this message]
2021-03-18  9:51 ` [Bug sanitizer/99179] asan failures with -Os on x86_64-apple-darwin iains at gcc dot gnu.org
2022-05-06  8:30 ` jakub at gcc dot gnu.org
2023-05-08 12:21 ` rguenth at gcc dot gnu.org

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-99179-4-LJqDH2480T@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).