[PATCH v3 0/4] Multi-context invalid breakpoint conditions and MI

[Tankut Baris Aktemur]

Hi,

This is v3 for

  https://sourceware.org/pipermail/gdb-patches/2021-April/177532.html

V2 is available at

  https://sourceware.org/pipermail/gdb-patches/2021-April/177578.html

In this revision, the 'cond' command skips the first "-" if it detects
that its argument string starts with "--force".  This way, both the
MI's -break-condition command and the CLI's cond command can flexibly
accept "--force" and "-force".  The documentation still uses "--force"
for MI and "-force" for CLI, though.

Simon Marchi (1):
  testsuite, gdb.mi: fix duplicate test names in mi-break.exp

Tankut Baris Aktemur (3):
  gdb/breakpoint: display "N" on MI for disabled-by-condition locations
  gdb/breakpoint: add a 'force_condition' parameter to
    'create_breakpoint'
  gdb/mi: add a '--force-condition' flag to the '-break-insert' cmd

 gdb/NEWS                          | 15 ++++++++
 gdb/breakpoint.c                  | 56 +++++++++++++++++++++++++-----
 gdb/breakpoint.h                  |  6 ++++
 gdb/doc/gdb.texinfo               | 29 ++++++++++++----
 gdb/guile/scm-breakpoint.c        |  2 +-
 gdb/mi/mi-cmd-break.c             |  7 ++++
 gdb/python/py-breakpoint.c        |  2 +-
 gdb/python/py-finishbreakpoint.c  |  2 +-
 gdb/testsuite/gdb.mi/mi-break.exp | 57 ++++++++++++++++++++++++++-----
 9 files changed, 149 insertions(+), 27 deletions(-)

-- 
2.17.1