Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: Automatically use hardware watchpoints
Date: Wed, 22 Nov 2006 10:44:00 -0000	[thread overview]
Message-ID: <200611221343.54968.vladimir@codesourcery.com> (raw)
In-Reply-To: <20061121222328.GA7268@nevyn.them.org>

On Wednesday 22 November 2006 01:23, Daniel Jacobowitz wrote:
> I accidentally typed break when I meant hbreak earlier today.  This
> patch was fortunately applied to that GDB.  It made me very happy
> to have this just work.
>
> The patch is OK for HEAD with minor corrections (plus Eli's doc
> requests).  Afterwards, I think this is NEWS-worthy (again, since
> there's a new command); we haven't always done that in the past,
> but I think it's a good idea :-)
>
> On Wed, Nov 01, 2006 at 02:47:40PM +0300, Vladimir Prus wrote:
> > +			  fprintf_filtered (gdb_stdout,
> > +					    _("Note: automatically using hardware breakpoints for read-only
> > addresses.\n"));
>
> Probably want
>
>        ... gdb_stdout, _("\
> Note:...");

I can't find this escape syntax in the C standard. Is this a gnu extension?

> > +	   made in insert_bp_location are preserved. */
>
> two spaces after period.
>
> And that's it :-)

Thanks, checked in.

- Volodya


  reply	other threads:[~2006-11-22 10:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-01 11:48 Vladimir Prus
2006-11-08 18:55 ` Vladimir Prus
2006-11-09 21:16   ` Eli Zaretskii
2006-11-21 22:23 ` Daniel Jacobowitz
2006-11-22 10:44   ` Vladimir Prus [this message]
2006-11-22 10:58     ` Andreas Schwab

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=200611221343.54968.vladimir@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sources.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