From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/3] Avoid printing global thread-id in CLI command output
Date: Wed, 8 Feb 2023 15:23:27 +0000 [thread overview]
Message-ID: <cover.1675869497.git.aburgess@redhat.com> (raw)
After fixing PR gdb/30087 I took a look through the rest of
breakpoint.c looking for places where we might be printing the global
thread-id. I found two places (patches #1 and #3).
While working on patch #1 I spotted that we handle the thread-id, but
not the task-id, so patch #2 fixes that.
---
Andrew Burgess (3):
gdb: don't print global thread-id to CLI in describe_other_breakpoints
gdb: show task number in describe_other_breakpoints
gdb: don't use the global thread-id in the saved breakpoints file
gdb/breakpoint.c | 12 +-
gdb/testsuite/gdb.ada/tasks.exp | 17 ++-
gdb/testsuite/gdb.multi/bp-thread-specific.c | 28 +++++
.../gdb.multi/bp-thread-specific.exp | 107 ++++++++++++++++++
4 files changed, 156 insertions(+), 8 deletions(-)
create mode 100644 gdb/testsuite/gdb.multi/bp-thread-specific.c
create mode 100644 gdb/testsuite/gdb.multi/bp-thread-specific.exp
base-commit: 1947a4a4bb7651a4656edceb1f9b246f96f89ebd
--
2.25.4
next reply other threads:[~2023-02-08 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:23 Andrew Burgess [this message]
2023-02-08 15:23 ` [PATCH 1/3] gdb: don't print global thread-id to CLI in describe_other_breakpoints Andrew Burgess
2023-02-08 17:55 ` Pedro Alves
2023-02-11 17:41 ` Andrew Burgess
2023-02-08 15:23 ` [PATCH 2/3] gdb: show task number " Andrew Burgess
2023-02-08 17:55 ` Pedro Alves
2023-02-11 17:42 ` Andrew Burgess
2023-02-08 15:23 ` [PATCH 3/3] gdb: don't use the global thread-id in the saved breakpoints file Andrew Burgess
2023-02-08 17:55 ` Pedro Alves
2023-02-10 19:22 ` Andrew Burgess
2023-02-17 17:49 ` Pedro Alves
2023-02-27 19:45 ` Andrew Burgess
2023-03-16 17:06 ` Andrew Burgess
2023-03-17 18:01 ` Pedro Alves
2023-03-20 10:38 ` 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.1675869497.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).