public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "pedro at palves dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27830] Attempt to resume already running thread Date: Tue, 21 Jun 2022 11:28:01 +0000 [thread overview] Message-ID: <bug-27830-4717-6JVHq4WW3O@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27830-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27830 Pedro Alves <pedro at palves dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pedro at palves dot net Status|NEW |ASSIGNED Assignee|unassigned at sourceware dot org |pedro at palves dot net --- Comment #4 from Pedro Alves <pedro at palves dot net> --- I've posted a series that fixes this, here: [PATCH 00/25] Step over thread clone and thread exit https://sourceware.org/pipermail/gdb-patches/2022-June/190181.html -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-06-21 11:28 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-07 14:16 [Bug gdb/27830] New: " andrew.burgess at embecosm dot com 2021-05-07 14:26 ` [Bug gdb/27830] " andrew.burgess at embecosm dot com 2021-05-10 17:27 ` andrew.burgess at embecosm dot com 2021-05-10 19:24 ` andrew.burgess at embecosm dot com 2022-06-21 11:28 ` pedro at palves dot net [this message] 2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org 2023-11-13 14:25 ` cvs-commit at gcc dot gnu.org 2023-11-13 15:00 ` pedro at palves dot 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-27830-4717-6JVHq4WW3O@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).