public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stsp at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/30041] pthread_cancel() hangs on aarch64
Date: Wed, 25 Jan 2023 10:57:32 +0000	[thread overview]
Message-ID: <bug-30041-131-52AAPxwHaF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30041-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30041

--- Comment #12 from Stas Sergeev <stsp at users dot sourceforge.net> ---
(In reply to Andreas Schwab from comment #11)
> Only one thread progresses.  The other is stuck in the shlib event.

So you mean gdb can't handle shlib
event because of SIGALRMs?
So is it a gdb bug which doesn't
stop signals while performing the
shlib event?
You told about gdb from the very
beginning, but only now I am starting
to understand what "shlib event" do
you mean.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-01-25 10:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 14:21 [Bug nptl/30041] New: pthread_cancel() hangs under gdb " stsp at users dot sourceforge.net
2023-01-24 14:52 ` [Bug nptl/30041] " schwab@linux-m68k.org
2023-01-24 15:25 ` stsp at users dot sourceforge.net
2023-01-24 15:34 ` stsp at users dot sourceforge.net
2023-01-24 15:41 ` schwab@linux-m68k.org
2023-01-24 15:55 ` stsp at users dot sourceforge.net
2023-01-24 18:20 ` stsp at users dot sourceforge.net
2023-01-24 18:20 ` [Bug nptl/30041] pthread_cancel() hangs " stsp at users dot sourceforge.net
2023-01-25  9:57 ` schwab@linux-m68k.org
2023-01-25 10:17 ` stsp at users dot sourceforge.net
2023-01-25 10:25 ` schwab@linux-m68k.org
2023-01-25 10:29 ` stsp at users dot sourceforge.net
2023-01-25 10:42 ` schwab@linux-m68k.org
2023-01-25 10:57 ` stsp at users dot sourceforge.net [this message]
2023-01-25 12:45 ` [Bug nptl/30041] pthread_cancel() hangs under gdb " stsp at users dot sourceforge.net

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-30041-131-52AAPxwHaF@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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: 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).