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

Message ID cover.1617806598.git.tankut.baris.aktemur@intel.com
Headers show
Series
  • Multi-context invalid breakpoint conditions and MI
Related show

Message

Simon Marchi via Gdb-patches April 7, 2021, 2:55 p.m.
Hi,

The starting point of this series is Jonah Graham's report at

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

When a bad breakpoint condition is used, the MI command
'-break-insert' inserts the breakpoint by disabling the breakpoint
locations.  This does not match the default CLI behavior, where the
breakpoint would be rejected unless the user explicitly uses the
'-force-condition' flag.  This series attempts to fix the problem and
align the MI behavior with CLI, together with some documentation
update.

Thanks
Baris


Tankut Baris Aktemur (4):
  gdb/doc: update the 'enabled' field's description for BP locations in
    MI
  testsuite, gdb.mi: fix duplicate test names in mi-break.exp
  gdb/breakpoint: add a 'force_condition' parameter to
    'create_breakpoint'
  gdb/mi: add a '-b' flag to the '-break-insert' cmd to force the
    condition

 gdb/NEWS                          |  7 ++++++
 gdb/breakpoint.c                  | 40 ++++++++++++++++++++++++++-----
 gdb/breakpoint.h                  |  6 +++++
 gdb/doc/gdb.texinfo               | 21 +++++++++++-----
 gdb/guile/scm-breakpoint.c        |  2 +-
 gdb/mi/mi-cmd-break.c             |  9 ++++++-
 gdb/python/py-breakpoint.c        |  2 +-
 gdb/python/py-finishbreakpoint.c  |  2 +-
 gdb/testsuite/gdb.mi/mi-break.exp | 39 ++++++++++++++++++++++++++----
 9 files changed, 108 insertions(+), 20 deletions(-)

-- 
2.17.1