[0/3] Avoid printing global thread-id in CLI command output

Message ID cover.1675869497.git.aburgess@redhat.com
Headers
Series Avoid printing global thread-id in CLI command output |

Message

Andrew Burgess Feb. 8, 2023, 3:23 p.m. UTC
  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