gdb: fix describe_other_breakpoints for default task being -1
authorAndrew Burgess <aburgess@redhat.com>
Sun, 12 Feb 2023 07:14:31 +0000 (07:14 +0000)
committerAndrew Burgess <aburgess@redhat.com>
Sun, 12 Feb 2023 07:19:25 +0000 (07:19 +0000)
commit8282ad74c302a8e0db7a588e500ae117a1df68c5
tree79ccbbc3dc570c6e76cee4028131160a197a663f
parentf0bdf68d3fb6db1dd2b83e07062e2104cdb785c2
gdb: fix describe_other_breakpoints for default task being -1

Commit:

  commit 2ecee236752932672fb3d6cd63c6976927f747d8
  CommitDate: Sun Feb 12 05:46:44 2023 +0000

      gdb: use -1 for breakpoint::task default value

Failed to take account of an earlier commit:

  commit f1f517e81039f6aa673b7d87a66bfbd25a66e3d3
  CommitDate: Sat Feb 11 17:36:24 2023 +0000

      gdb: show task number in describe_other_breakpoints

That both of these are my own commits is only more embarrassing.

This small fix updates describe_other_breakpoints to take account of
the default task number now being -1.  This fixes regressions in
gdb.base/break.exp, gdb.base/break-always.exp, and many other tests.
gdb/breakpoint.c