Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: S?rgio Durigan J?nior <sergiodj@linux.vnet.ibm.com>,
		gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] 'catch syscall' feature -- 	Architecture-independent part
Date: Fri, 10 Oct 2008 13:12:00 -0000	[thread overview]
Message-ID: <20081010131204.GB9073@caradoc.them.org> (raw)
In-Reply-To: <20081006172136.GA3588@adacore.com>

On Mon, Oct 06, 2008 at 01:21:36PM -0400, Joel Brobecker wrote:
> 2008-10-06  Joel Brobecker  <brobecker@adacore.com>
> 
>         * breakpoint.h (enum bptype): New enum bp_catchpoint.
>         Delete bp_catch_fork and bp_catch_vfork.
>         * breakpoint.c: Implement the catch fork/vfork feature
>         using the bp_catchpoint bptype enum and the breakpoint_ops
>         structure.  Remove the use of bp_catch_fork and bp_catch_vfork
>         breakpoint kinds.

I think this is sufficiently non-mechanical that we should be more
descriptive in the changelog.

> @@ -1505,6 +1498,14 @@ update_breakpoints_after_exec (void)
>  	continue;
>        }
>  
> +    if (b->type == bp_catchpoint)
> +      {
> +        /* For now, none of the bp_catchpoint breakpoints need to
> +           do anything at this point.  In the future, if some of
> +           the catchpoints need to something, we will need to add
> +           a new method, and call this method from here.  */
> +      }
> +
>      /* Don't delete an exec catchpoint, because else the inferior
>         won't stop when it ought!
>  
> @@ -1513,9 +1514,7 @@ update_breakpoints_after_exec (void)
>         seen, but only when the subsequent exec is seen.  (And because
>         deleting fork catchpoints here but not vfork catchpoints will
>         seem mysterious to users, keep those too.)  */
> -    if ((b->type == bp_catch_exec) ||
> -	(b->type == bp_catch_vfork) ||
> -	(b->type == bp_catch_fork))
> +    if (b->type == bp_catch_exec)
>        {
>  	continue;
>        }

This bit changes behavior (and the old comment doesn't make sense any
more).

> -	case bp_catch_fork:
> -	case bp_catch_vfork:
> +        case bp_catchpoint:

Spaces/tabs?

> @@ -3939,10 +3900,9 @@ user_settable_breakpoint (const struct b
>  user_settable_breakpoint (const struct breakpoint *b)
>  {
>    return (b->type == bp_breakpoint
> +          || b->type == bp_catchpoint
>  	  || b->type == bp_catch_load
>  	  || b->type == bp_catch_unload
> -	  || b->type == bp_catch_fork
> -	  || b->type == bp_catch_vfork

Spaces/tabs again.

> @@ -4163,9 +4123,8 @@ breakpoint_address_is_meaningful (struct
>  	  && type != bp_hardware_watchpoint
>  	  && type != bp_read_watchpoint
>  	  && type != bp_access_watchpoint
> -	  && type != bp_catch_exec
> -	  && type != bp_catch_fork
> -	  && type != bp_catch_vfork);
> +          && type != bp_catchpoint
> +	  && type != bp_catch_exec);
>  }
>  
>  /* Rescan breakpoints at the same address and section as BPT,

Likewise.

Anyway, that was all trivial.  It looks good to me.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-10-10 13:12 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-30 18:12 Sérgio Durigan Júnior
2008-10-02 21:13 ` Joel Brobecker
2008-10-03  2:33   ` Sérgio Durigan Júnior
2008-10-03  6:07     ` Joel Brobecker
2008-10-03 17:52       ` Daniel Jacobowitz
2008-10-04 23:07         ` Sérgio Durigan Júnior
2008-10-04 23:04       ` Sérgio Durigan Júnior
2008-10-06 17:22         ` Joel Brobecker
2008-10-10 13:12           ` Daniel Jacobowitz [this message]
2008-10-10 15:28           ` Sérgio Durigan Júnior
2008-10-12  2:26           ` Sérgio Durigan Júnior
2008-10-15  5:40             ` Joel Brobecker
2008-10-16  3:35               ` Sérgio Durigan Júnior
2008-10-16 12:37                 ` Daniel Jacobowitz
2008-10-16 15:17                   ` Daniel Jacobowitz
2008-10-16 16:28                     ` Joel Brobecker
2008-11-04  4:32 Sérgio Durigan Júnior
2008-11-04 16:17 ` Pedro Alves
2008-11-07  3:30   ` Sérgio Durigan Júnior
2008-11-07 12:12     ` Pedro Alves
2008-11-07 13:30       ` Daniel Jacobowitz
2008-11-08 15:35       ` Sérgio Durigan Júnior
2008-11-04 17:57 ` Tom Tromey
2008-11-04 21:55   ` Thiago Jung Bauermann
2008-11-04 22:33     ` Tom Tromey
2008-11-05 19:05       ` Tom Tromey
2008-11-05 19:13         ` Sérgio Durigan Júnior
2008-11-07  3:41         ` Sérgio Durigan Júnior
2008-11-07  3:39   ` Sérgio Durigan Júnior
2008-11-07 18:21     ` Tom Tromey
2008-11-04 21:13 ` Eli Zaretskii
2008-11-04 22:12   ` Thiago Jung Bauermann
2008-11-04 22:22     ` Eli Zaretskii
2008-11-04 22:35       ` Daniel Jacobowitz
2008-11-05  4:19         ` Eli Zaretskii
2008-11-05 13:34           ` Sérgio Durigan Júnior
2008-11-05 18:42             ` Eli Zaretskii
2008-11-08 19:31             ` Mark Kettenis
2008-11-05 14:55           ` Daniel Jacobowitz
2008-11-05 18:43             ` Eli Zaretskii
2008-11-05 18:59               ` Daniel Jacobowitz
2008-11-05 19:11                 ` Eli Zaretskii
2008-11-06 23:03               ` Mark Kettenis
2008-11-04 22:31     ` Pedro Alves
2008-11-05  4:10       ` Eli Zaretskii
2008-11-05 12:29         ` Pedro Alves
2008-11-05 18:38           ` Eli Zaretskii
2008-11-05 18:57             ` Pedro Alves
2008-11-05 19:10               ` Eli Zaretskii
2008-11-05 19:34                 ` Pedro Alves
2008-11-05 20:36                   ` Eli Zaretskii
2008-11-05 21:10                     ` Pedro Alves
2008-11-06  4:27                       ` Eli Zaretskii
2008-11-06 14:32                         ` Pedro Alves
2008-11-07  9:59                           ` Eli Zaretskii
2008-11-07 10:10                             ` Pedro Alves
2008-11-05 13:32         ` Mark Kettenis

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=20081010131204.GB9073@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@linux.vnet.ibm.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