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

[Aktemur, Tankut Baris]

On Wednesday, July 22, 2020 8:24 PM, Pedro Alves wrote:
> On 7/21/20 10:08 AM, Tankut Baris Aktemur via Gdb-patches wrote:
> >> 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.
> >
> >
> > Kindly pinging for
> >
> >   https://sourceware.org/pipermail/gdb-patches/2020-June/169954.html
> 
> I'm confused -- are you proposing to merge patch #2 as it was,
> or with the two passes?

Sorry for the confusion.  Please consider the two-pass version.

Thanks
-Baris


Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Gary Kershaw
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928