Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: Kevin Pouget <kevin.pouget@gmail.com>
Cc: Tom Tromey <tromey@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove same-pc breakpoint notification for internal BPs
Date: Mon, 05 Sep 2011 14:43:00 -0000	[thread overview]
Message-ID: <201109051256.24817.pedro@codesourcery.com> (raw)
In-Reply-To: <CAPftXULPpkOqU_zBiRMxJDdpOWWpKxdvAFdi0NBYgn1Q7FnKmg@mail.gmail.com>

On Wednesday 31 August 2011 14:18:00, Kevin Pouget wrote:
> On Wed, Apr 27, 2011 at 3:02 PM, Kevin Pouget <kevin.pouget@gmail.com> wrote:
> > Hello,
> >
> > here is an updated version of the patch, which uses `user_breakpoint_p'
> >
> >
> > thanks,
> >
> > Kevin (still waiting for copyright papers)
> 
> 
> Hello,
> 
> this patch was not explicitly approved when I first submitted it,  but
> all the concerns were addressed; please let me not if it looks good to
> you

This is okay, thanks.  

On Wednesday 31 August 2011 14:18:00, Kevin Pouget wrote:
>    ALL_BREAKPOINTS (b)
> -    others += breakpoint_has_pc (b, pspace, pc, section);
> +    others += (breakpoint_has_pc (b, pspace, pc, section)
> +               && user_breakpoint_p (b));
>    if (others > 0)
>      {
>        if (others == 1)
> @@ -5418,7 +5419,7 @@ describe_other_breakpoints (struct gdbarch *gdbarch,
>        else /* if (others == ???) */
>         printf_filtered (_("Note: breakpoints "));
>        ALL_BREAKPOINTS (b)
> -       if (breakpoint_has_pc (b, pspace, pc, section))
> +       if (breakpoint_has_pc (b, pspace, pc, section) && user_breakpoint_p (b))


I'd suggest flipping the tests order so the cheaper test is done
first, like:

> +    others += (user_breakpoint_p (b)
> +               && breakpoint_has_pc (b, pspace, pc, section));

and 

> +       if (user_breakpoint_p (b) && breakpoint_has_pc (b, pspace, pc, section))

Okay with or without that change.

-- 
Pedro Alves


  reply	other threads:[~2011-09-05 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 13:44 Kevin Pouget
2011-04-20 13:57 ` Kevin Pouget
2011-04-20 19:03 ` Tom Tromey
2011-04-21  8:12   ` Kevin Pouget
2011-04-21  8:49     ` Pedro Alves
2011-04-21  9:25       ` Kevin Pouget
2011-04-21  9:34         ` Kevin Pouget
2011-04-21 14:17       ` Tom Tromey
2011-04-21 14:59         ` Pedro Alves
2011-04-21 15:06           ` Tom Tromey
2011-04-21 15:27             ` Pedro Alves
2011-04-27 13:03               ` Kevin Pouget
2011-08-31 13:18                 ` Kevin Pouget
2011-09-05 14:43                   ` Pedro Alves [this message]
2011-09-15 12:31                     ` Kevin Pouget

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=201109051256.24817.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevin.pouget@gmail.com \
    --cc=tromey@redhat.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