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

On Thursday 21 April 2011 15:17:26, Tom Tromey wrote:
> I wonder if this code should be using user_breakpoint_p instead.

I never understood why we need that function (as is implemented) though.

  /* Return non-zero if B is user settable (breakpoints, watchpoints,
     catchpoints, et.al.).  */

  static int
  user_settable_breakpoint (const struct breakpoint *b)
  {
      return (b->type == bp_breakpoint
  	  || b->type == bp_catchpoint
  	  || b->type == bp_hardware_breakpoint
  	  || is_tracepoint (b)
  	  || is_watchpoint (b)
  	  || b->type == bp_gnu_ifunc_resolver);
  }

  /* Return true if this breakpoint was set by the user, false if it is
     internal or momentary.  */

  int
  user_breakpoint_p (struct breakpoint *b)
  {
    return user_settable_breakpoint (b) && b->number > 0;
  }

What could be !user_settable_breakpoint whose b->number is > 0?
IOW, why isn't that just :

  int
  user_breakpoint_p (struct breakpoint *b)
  {
    return b->number > 0;
  }

?

There are a bunch of places that check b->number directly.

-- 
Pedro Alves


  reply	other threads:[~2011-04-21 14:59 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 [this message]
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
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=201104211559.40948.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