Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <muller@ics.u-strasbg.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFA] breakpoint.c ARI fixes
Date: Tue, 09 Jun 2009 21:15:00 -0000	[thread overview]
Message-ID: <m3d49dhzxi.fsf@fleche.redhat.com> (raw)
In-Reply-To: <000301c9e8cb$e8592050$b90b60f0$@u-strasbg.fr> (Pierre Muller's message of "Tue\, 9 Jun 2009 08\:31\:21 +0200")

>>>>> "Pierre" == Pierre Muller <muller@ics.u-strasbg.fr> writes:

Pierre>   The reason why I didn't check them in as obvious
Pierre> is only that for some of the if assignment rules,
Pierre> the assignment appear as a second test, meaning
Pierre> that it is not always executed in old code, while it is 
Pierre> in new code in print_one_breakpoint_location.

[...]

Pierre>    Is this OK?

Yes.  Thanks for working on this.

Pierre> I would like to know if the minimal ChangeLog
Pierre> below is enough or if I should use the long version
Pierre> listing all modified functions.

You must list them all, I'm afraid.

Pierre> +      if ((bsp->breakpoint_at != NULL)
Pierre> +	  && (bsp->breakpoint_at->owner->type == bp_step_resume)
Pierre> +	  && (bsp->breakpoint_at->owner->thread == current_thread
Pierre> +	      || bsp->breakpoint_at->owner->thread == -1))

Pierre> +  if ((ex_event != EX_EVENT_THROW)
Pierre> +      && (ex_event != EX_EVENT_CATCH))

As long as you are fixing some formatting stuff, you might as well
remove the extra parens from these expressions.

Tom


  reply	other threads:[~2009-06-09 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09  6:31 Pierre Muller
2009-06-09 21:15 ` Tom Tromey [this message]
2009-06-10  4:34   ` Pierre Muller

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=m3d49dhzxi.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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