From: Pedro Alves <palves@redhat.com>
To: Christian Biesinger <cbiesinger@google.com>
Cc: Simon Marchi <simark@simark.ca>,
Keno Fischer <keno@juliacomputing.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Stop considering hw and sw breakpoints duplicates (Re: [PATCH] breakpoint: Make sure location types match before swapping)
Date: Tue, 21 Apr 2020 19:31:51 +0100 [thread overview]
Message-ID: <d4bbc5dd-ae40-0af9-015a-13be83d7a541@redhat.com> (raw)
In-Reply-To: <CAPTJ0XG1S3rYT_eb7Y9n8QNJvwgQgLbMdfnLucuWS3jt-vnpTA@mail.gmail.com>
On 4/21/20 5:24 PM, Christian Biesinger via Gdb-patches wrote:
> On Sun, Apr 19, 2020 at 1:49 PM Pedro Alves via Gdb-patches
> <gdb-patches@sourceware.org> wrote:
>> From 10d0944768e6ce59861c1522ed48449422a76736 Mon Sep 17 00:00:00 2001
>> From: Pedro Alves <palves@redhat.com>
>> Date: Sun, 19 Apr 2020 18:25:55 +0100
>> Subject: [PATCH] Stop considering hw and sw breakpoints duplicates
>>
>> ---
>> gdb/breakpoint.c | 269 ++++++++++++++-------
>> gdb/testsuite/gdb.base/breakpoint-in-ro-region.exp | 2 +-
>> 2 files changed, 183 insertions(+), 88 deletions(-)
>>
>> diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
>> index e49025461ba..27799e89807 100644
>> --- a/gdb/breakpoint.c
>> +++ b/gdb/breakpoint.c
>> @@ -144,6 +144,10 @@ static void describe_other_breakpoints (struct gdbarch *,
>> static int watchpoint_locations_match (struct bp_location *loc1,
>> struct bp_location *loc2);
>>
>> +static int breakpoint_locations_match (struct bp_location *loc1,
>> + struct bp_location *loc2,
>> + bool sw_hw_bps_match = false);
>> +
>
> Should this return a bool?
>
>> static int breakpoint_location_address_match (struct bp_location *bl,
>> const struct address_space *aspace,
>> CORE_ADDR addr);
>
> And this, I guess.
Yeah, they should. Old, pre-C++ code.
It feels like an orthogonal change though, particularly since I think we
could change all of those two, plus watchpoint_locations_match at the
same time.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2020-04-21 18:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 1:38 [PATCH] breakpoint: Make sure location types match before swapping Keno Fischer
2020-04-14 7:01 ` Keno Fischer
2020-04-14 15:04 ` Simon Marchi
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 [this message]
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=d4bbc5dd-ae40-0af9-015a-13be83d7a541@redhat.com \
--to=palves@redhat.com \
--cc=cbiesinger@google.com \
--cc=gdb-patches@sourceware.org \
--cc=keno@juliacomputing.com \
--cc=simark@simark.ca \
/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