[PATCH 0/3] Prevent bad conditions from putting breakpoints into broken state

[Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>]

Hi,

If the condition of a breakpoint is "bad" (e.g. has unresolved
symbols, syntax errors, etc.), the breakpoint goes into a broken state
where the condition string or the condition expressions are updated
inadvertently.  This small series attempts to fix that.

Regards.
Baris

Tankut Baris Aktemur (3):
  gdb/breakpoint: do not update the condition string if parsing the
    condition fails
  gdb/breakpoint: set the condition exp after parsing the condition
    successfully
  gdb/breakpoint: refactor 'set_breakpoint_condition'

 gdb/breakpoint.c                         |  70 ++++++-------
 gdb/testsuite/gdb.base/condbreak-bad.c   |  24 +++++
 gdb/testsuite/gdb.base/condbreak-bad.exp | 128 +++++++++++++++++++++++
 3 files changed, 183 insertions(+), 39 deletions(-)
 create mode 100644 gdb/testsuite/gdb.base/condbreak-bad.c
 create mode 100644 gdb/testsuite/gdb.base/condbreak-bad.exp

-- 
2.17.1