From: Daniel Jacobowitz <drow@mvista.com>
To: Pierre Muller <muller@ics.u-strasbg.fr>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb-patches@sources.redhat.com
Subject: Re: Resend: [RFA] Fix problem with i386 watchpoints after restarting
Date: Thu, 04 Jul 2002 09:34:00 -0000 [thread overview]
Message-ID: <20020704162544.GA26409@nevyn.them.org> (raw)
In-Reply-To: <4.2.0.58.20020704143015.02832028@ics.u-strasbg.fr>
On Thu, Jul 04, 2002 at 03:12:46PM +0200, Pierre Muller wrote:
> At 15:35 17/06/2002 , Pierre Muller a écrit:
> >At 12:16 13/06/2002 , Mark Kettenis a écrit:
> > >Sorry, I somehow missed your earlier message. This seems to me as an
> > >acceptable way to solve the problem (although I still think there is
> > >something wrong with GDB's mechanism of removing hardware breakpoints.
> > >But: could you add the reason why this is needed to the comment.
> > >Minor nit: Please end your sentences with a '.' and put two spaces
> > >after it.
> >OK, I slightly modifed the patch
> >by adding a comment to i386-nat.c
> >and correcting the comment in the nm-i386.h file.
> >
> >Can I check this in?
>
> After getting approval by a private mail, I have
> checked this in.
Is this appropriate for the branch also? My instincts say yes.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-07-04 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 0:20 Pierre Muller
2002-06-13 3:16 ` Mark Kettenis
2002-06-17 6:38 ` Pierre Muller
2002-07-04 6:45 ` Pierre Muller
2002-07-04 9:34 ` Daniel Jacobowitz [this message]
2002-07-04 9:37 ` Pierre Muller
2002-07-08 13:39 ` Andrew Cagney
2002-07-08 13:54 ` Mark Kettenis
2002-07-08 22:31 ` Eli Zaretskii
2002-07-09 1:40 ` Pierre Muller
2002-07-09 7:15 ` Pierre Muller
2002-07-09 7:50 ` Andrew Cagney
2002-07-09 8:34 ` Michal Ludvig
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=20020704162544.GA26409@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
--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