public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27830] Attempt to resume already running thread
Date: Mon, 13 Nov 2023 14:25:49 +0000	[thread overview]
Message-ID: <bug-27830-4717-i6uLfSvbV3@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27830-4717@http.sourceware.org/bugzilla/>

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

--- Comment #8 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Pedro Alves <palves@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=25b16bc9e791d53028c3c180125a80f345b97d94

commit 25b16bc9e791d53028c3c180125a80f345b97d94
Author: Pedro Alves <pedro@palves.net>
Date:   Tue Nov 23 20:35:12 2021 +0000

    Thread options & clone events (native Linux)

    This commit teaches the native Linux target about the
    GDB_THREAD_OPTION_CLONE thread option.  It's actually simpler to just
    continue reporting all clone events unconditionally to the core.
    There's never any harm in reporting a clone event when the option is
    disabled.  All we need to do is to report support for the option,
    otherwise GDB falls back to use target_thread_events().

    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=19675
    Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=27830
    Reviewed-By: Andrew Burgess <aburgess@redhat.com>
    Change-Id: If90316e2dcd0c61d0fefa0d463c046011698acf9

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

  parent reply	other threads:[~2023-11-13 14:25 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
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 [this message]
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-i6uLfSvbV3@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: 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).