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

Tankut Baris Aktemur via Gdb-patches
2021-04-08T14:23:06Z

Hi,

This is v2 of

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

The changes with respect to v1 are:

* Using a table in the documentation of the 'enabled' field in MI output.

* Displaying "N" instead of "N*" in MI for locations that are disabled
because of the breakpoint condition.

* Using proc_with_prefix to eliminate duplicate test names in
gdb.mi/mi-break.exp.

* Using "--force-condition" instead of "-b" as a flag for the MI's
-break-insert command.

* Revising the tests to check for command completion ("^done")
and using 'mi_make_breakpoint_multi' to check for the 'enabled="N"'
field.

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 | 8 +++++
gdb/breakpoint.c | 48 +++++++++++++++++++++-----
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, 134 insertions(+), 27 deletions(-)

--
2.17.1