public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Prevent combining 'task' and 'thread' keywords
Date: Wed,  8 Feb 2023 15:16:15 +0000	[thread overview]
Message-ID: <cover.1675869267.git.aburgess@redhat.com> (raw)

Inspired by a recent conversation about the expected behaviour of the
'thread' and 'task' keywords when combined together, this series
prohibits such combinations.  And then does a related code cleanup.

---

Andrew Burgess (2):
  gdb: only allow one of thread or task on breakpoints or watchpoints
  gdb: use -1 for breakpoint::task default value

 gdb/NEWS                        |  6 +++
 gdb/breakpoint.c                | 56 ++++++++++++++++------
 gdb/breakpoint.h                | 14 +++++-
 gdb/guile/scm-breakpoint.c      | 14 +++++-
 gdb/python/py-breakpoint.c      | 18 ++++++-
 gdb/testsuite/gdb.ada/tasks.exp | 85 +++++++++++++++++++++++++++++++--
 6 files changed, 169 insertions(+), 24 deletions(-)


base-commit: 1947a4a4bb7651a4656edceb1f9b246f96f89ebd
-- 
2.25.4


             reply	other threads:[~2023-02-08 15:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 15:16 Andrew Burgess [this message]
2023-02-08 15:16 ` [PATCH 1/2] gdb: only allow one of thread or task on breakpoints or watchpoints Andrew Burgess
2023-02-08 15:52   ` Eli Zaretskii
2023-02-08 18:10   ` Pedro Alves
2023-02-12  5:50     ` Andrew Burgess
2023-02-12 22:58       ` Tom Tromey
2023-02-13 11:26         ` Andrew Burgess
2023-02-08 15:16 ` [PATCH 2/2] gdb: use -1 for breakpoint::task default value Andrew Burgess
2023-02-08 18:10   ` Pedro Alves
2023-02-12  7:23     ` Andrew Burgess

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=cover.1675869267.git.aburgess@redhat.com \
    --to=aburgess@redhat.com \
    --cc=gdb-patches@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).