public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/103978] AddressSanitizer CHECK failed with threads and thread canceling with glibc 2.28+
Date: Wed, 12 Jan 2022 07:48:03 +0000	[thread overview]
Message-ID: <bug-103978-4-PeFxakqtiP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103978-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Could there be some ordering issues with pthread_key going on?
2.28 added C11 thread.h support which did touch pthread_key too.

  parent reply	other threads:[~2022-01-12  7:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 15:14 [Bug sanitizer/103978] New: AddressSanitizer CHECK failed ../../../../src/libsanitizer/asan/asan_thread.cpp:367 "((ptr[0] == kCurrentStackFrameMagic)) != (0)" (0x0, 0x0) contino at epigenesys dot com
2022-01-11 15:22 ` [Bug sanitizer/103978] " marxin at gcc dot gnu.org
2022-01-12  7:31 ` [Bug sanitizer/103978] [11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-12  7:33 ` pinskia at gcc dot gnu.org
2022-01-12  7:37 ` [Bug sanitizer/103978] AddressSanitizer CHECK failed with threads and thread canceling with glibc 2.28+ pinskia at gcc dot gnu.org
2022-01-12  7:40 ` pinskia at gcc dot gnu.org
2022-01-12  7:48 ` pinskia at gcc dot gnu.org [this message]
2022-01-12  7:51 ` pinskia at gcc dot gnu.org
2022-01-12  8:00 ` pinskia at gcc dot gnu.org
2022-01-12  8:08 ` pinskia at gcc dot gnu.org
2022-01-12 15:37 ` hjl.tools at gmail dot com
2022-01-21  9:43 ` 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-103978-4-PeFxakqtiP@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).