public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug threads/26228] FAIL: gdb.threads/create-fail.exp: iteration x: run till end (SIG32) Date: Thu, 04 Feb 2021 17:27:41 +0000 [thread overview] Message-ID: <bug-26228-4717-JWYJzc0WlP@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26228-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26228 --- Comment #10 from Tom de Vries <vries at gcc dot gnu.org> --- Found while trying to reproduce root cause: current root cause for me is: since glibc 2.28, sigaddset ignores SIGCANCEL, which means lin_thread_get_thread_signals is broken. This needs to be fixed differently. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-04 17:27 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-11 8:35 [Bug threads/26228] New: " vries at gcc dot gnu.org 2020-07-11 8:52 ` [Bug threads/26228] " vries at gcc dot gnu.org 2020-07-11 9:11 ` vries at gcc dot gnu.org 2020-07-24 13:59 ` vries at gcc dot gnu.org 2021-02-01 21:44 ` vries at gcc dot gnu.org 2021-02-02 11:55 ` luis.machado at linaro dot org 2021-02-04 13:27 ` vries at gcc dot gnu.org 2021-02-04 14:11 ` luis.machado at linaro dot org 2021-02-04 14:15 ` vries at gcc dot gnu.org 2021-02-04 14:24 ` luis.machado at linaro dot org 2021-02-04 17:27 ` vries at gcc dot gnu.org [this message] 2021-02-12 19:12 ` cvs-commit at gcc dot gnu.org 2021-02-12 19:13 ` vries 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-26228-4717-JWYJzc0WlP@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.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: linkBe 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).