public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/101476] AddressSanitizer check failed, points out a (potentially) non-existing stack error and pthread_cancel
Date: Tue, 25 Jan 2022 11:25:15 +0000 [thread overview]
Message-ID: <bug-101476-4-UEfUXlP1gm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101476-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101476
--- Comment #14 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Stas Sergeev from comment #13)
> Found another problem.
> https://github.com/gcc-mirror/gcc/blob/master/libsanitizer/asan/asan_posix.
> cpp#L53
> The comment above that line talks about
> SS_AUTODISARM, but the line itself does
> not account for any flags. In a mean time,
> linux returns SS_DISABLE in combination
> with flags, like SS_AUTODISARM. So the
> "!=" check should not be used.
>
> My app probes for SS_AUTODISARM by trying
> to set it, and after that, asan breaks.
> This is quite cludgy though.
> Should the check be changed to
> if (!(signal_stack.ss_flags & SS_DISABLE))
> or maybe linux should not return any flags
> together with SS_DISABLE?
> man page talks "strange things" on that subject.
Please report to upstream as well.
next prev parent reply other threads:[~2022-01-25 11:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 19:43 [Bug sanitizer/101476] New: AddressSanitizer check failed, points out a (potentially) non-existing stack error franek.balcerak at o2 dot pl
2021-07-22 10:19 ` [Bug sanitizer/101476] " marxin at gcc dot gnu.org
2022-01-18 17:01 ` stsp at users dot sourceforge.net
2022-01-18 17:56 ` stsp at users dot sourceforge.net
2022-01-18 18:14 ` stsp at users dot sourceforge.net
2022-01-18 20:24 ` stsp at users dot sourceforge.net
2022-01-18 22:23 ` stsp at users dot sourceforge.net
2022-01-18 23:01 ` stsp at users dot sourceforge.net
2022-01-19 9:04 ` marxin at gcc dot gnu.org
2022-01-19 14:02 ` stsp at users dot sourceforge.net
2022-01-19 14:13 ` marxin at gcc dot gnu.org
2022-01-20 9:58 ` stsp at users dot sourceforge.net
2022-01-21 9:43 ` pinskia at gcc dot gnu.org
2022-01-25 10:35 ` [Bug sanitizer/101476] AddressSanitizer check failed, points out a (potentially) non-existing stack error and pthread_cancel stsp at users dot sourceforge.net
2022-01-25 11:25 ` marxin at gcc dot gnu.org [this message]
2022-01-25 11:31 ` stsp at users dot sourceforge.net
2022-01-25 18:28 ` stsp at users dot sourceforge.net
2022-02-11 12:45 ` stsp at users dot sourceforge.net
2022-10-18 18:03 ` stsp at users dot sourceforge.net
2023-03-19 16:58 ` pinskia 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-101476-4-UEfUXlP1gm@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).