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

Aktemur, Tankut Baris via Gdb-patches
2021-04-07T07:09:19Z

Hi Jonah,

On Tuesday, April 6, 2021 4:37 PM, Jonah Graham wrote:
> Great. AFAICT -break-insert with a condition included always acts as if -force-condition was included. i.e. "break method -force-condition if symbol" is equivalent to "26-break-insert -c symbol -f method"

Yes, this is the current behavior but it's unintentional.
I'm preparing a patch to fix this.

> I assume therefore that "N*" in a reply to break-insert always means "warning: failed to validate condition
at location 1, disabling:" (What does the "1" refer to? IIUC it is the ".1" in the breakpoint number?).

Yes and yes. A breakpoint may have multiple locations. The "1" here refers
to the location number; i.e. the ".1" suffix in the breakpoint location number.

> In the breakpoint table N* always means "Breakpoint condition is invalid at this location" and that the breakpoint is disabled?

Only the particular location is disabled. There may be other
locations that are still enabled (y) or disabled by the user (n).
Also note that "N*" may appear in the table for a location only,
not the breakpoint itself.

Regards.
-Baris

Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928