[0/2] Breakpoint conditions at locations with differing contexts

Message ID cover.1596207808.git.tankut.baris.aktemur@intel.com
Headers show
  • Breakpoint conditions at locations with differing contexts
Related show


Eli Zaretskii via Gdb-patches July 31, 2020, 3:42 p.m.

This is a short series about conditional breakpoints where the
condition may be invalid at some breakpoint locations because of their
context.  Currently, GDB does not allow defining a condition if it's
not valid at all locations.  This series aims at bringing more
flexibility: the locations at which the condition expression is
invalid are disabled automatically.

The first patch is the one that implements the new behavior.
The second one is an RFC.  Depending on the community comments,
I'd like to take a direction and complete it.


Tankut Baris Aktemur (2):
  gdb/breakpoint: disable a bp location if condition is invalid at that
  gdb/breakpoint: add a '-force' flag to the 'condition' command

 gdb/ada-lang.c                                |   2 +-
 gdb/breakpoint.c                              | 224 ++++++++++++++----
 gdb/breakpoint.h                              |  12 +-
 gdb/doc/gdb.texinfo                           |   6 +
 gdb/guile/scm-breakpoint.c                    |   2 +-
 gdb/python/py-breakpoint.c                    |   2 +-
 .../condbreak-multi-context-included.c        |  18 ++
 .../gdb.base/condbreak-multi-context.c        |  51 ++++
 .../gdb.base/condbreak-multi-context.exp      | 218 +++++++++++++++++
 9 files changed, 478 insertions(+), 57 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/condbreak-multi-context-included.c
 create mode 100644 gdb/testsuite/gdb.base/condbreak-multi-context.c
 create mode 100644 gdb/testsuite/gdb.base/condbreak-multi-context.exp