From: Simon Marchi <simark@simark.ca>
To: Keno Fischer <keno@juliacomputing.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] breakpoint: Make sure location types match before swapping
Date: Tue, 14 Apr 2020 11:04:47 -0400 [thread overview]
Message-ID: <372f95e1-4591-7e0d-90c7-168477e032ba@simark.ca> (raw)
In-Reply-To: <CABV8kRz_h9LX2DzMeixAjfmkCRoxomqJg824dr+n4JHuN7O0Fg@mail.gmail.com>
On 2020-04-14 3:01 a.m., Keno Fischer wrote:
> Bump. It would be great to get this fixed.
>
> On Tue, Mar 31, 2020 at 9:38 PM Keno Fischer <keno@juliacomputing.com> wrote:
>>
>> This patch fixes PR gdb/25741 "GDB tries to set breakpoint using Z0, but remove it using z1".
>> In particular, what occurs in that case is that a hardware breakpoint is hit,
>> after which GDB removes it and establishes a single step breakpoint at the
>> same location. Afterwards, rather than simply removing this breakpoint and
>> re-enabling the hardware breakpoint, GDB simply swaps the activation, without
>> informing the server, leading to an inconsistency in GDB's view of the world
>> and the server's view of the world. To remidy this situation, this
>> patch adds a check that ensures two breakpoint locations have the
>> same type before they are considered equal and thus eligible for silent
>> swapping.
>>
>> gdb/ChangeLog:
>> * breakpoint.c (breakpoint_locations_match): Fix PR gdb/25741
>>
>> Signed-off-by: Keno Fischer <keno@juliacomputing.com>
>> ---
>> gdb/breakpoint.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
>> index e49025461b..582dae1946 100644
>> --- a/gdb/breakpoint.c
>> +++ b/gdb/breakpoint.c
>> @@ -6838,7 +6838,7 @@ breakpoint_locations_match (struct bp_location *loc1,
>> /* We compare bp_location.length in order to cover ranged breakpoints. */
>> return (breakpoint_address_match (loc1->pspace->aspace, loc1->address,
>> loc2->pspace->aspace, loc2->address)
>> - && loc1->length == loc2->length);
>> + && loc1->length == loc2->length && loc1->loc_type == loc2->loc_type);
>> }
>>
>> static void
>> --
>> 2.24.0
>>
I think the change makes sense, but this is not an area I know well, and it's one that
is a bit sensitive. I'll do a full test run and take a bit more time to look at it.
In the mean time, if anybody else wants to take a look, go for it.
Simon
next prev parent reply other threads:[~2020-04-14 15:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 1:38 Keno Fischer
2020-04-14 7:01 ` Keno Fischer
2020-04-14 15:04 ` Simon Marchi [this message]
2020-04-14 16:00 ` Andrew Burgess
2020-04-14 16:26 ` Keno Fischer
2020-04-14 19:17 ` Pedro Alves
2020-04-15 20:46 ` Andrew Burgess
2020-04-17 12:28 ` Andrew Burgess
2020-04-17 17:22 ` Pedro Alves
2020-04-19 18:21 ` Pedro Alves
2020-04-19 18:49 ` [PATCH] Stop considering hw and sw breakpoints duplicates (Re: [PATCH] breakpoint: Make sure location types match before swapping) Pedro Alves
2020-04-20 9:02 ` Andrew Burgess
2020-04-21 16:24 ` Christian Biesinger
2020-04-21 18:31 ` Pedro Alves
2020-05-02 20:13 ` [PATCH v2] Stop considering hw and sw breakpoint locations duplicates (PR gdb/25741) Pedro Alves
2020-05-17 18:25 ` Pedro Alves
2020-05-17 18:50 ` Keno Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=372f95e1-4591-7e0d-90c7-168477e032ba@simark.ca \
--to=simark@simark.ca \
--cc=gdb-patches@sourceware.org \
--cc=keno@juliacomputing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox