Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Michael Snyder <msnyder@vmware.com>
Subject: Re: [patch] Error reporting during insert_breakpoints
Date: Wed, 03 Jun 2009 22:10:00 -0000	[thread overview]
Message-ID: <200906032311.08737.pedro@codesourcery.com> (raw)
In-Reply-To: <200906032246.44508.pedro@codesourcery.com>

On Wednesday 03 June 2009 22:46:44, Pedro Alves wrote:
> > @@ -1223,10 +1223,10 @@ Note: automatically using hardware break
> >               else
> >                 {
> >                   fprintf_unfiltered (tmp_error_stream, 
> > -                                     "Cannot insert breakpoint %d.\n", 
> > +                                     "Cannot insert breakpoint %d", 
> >                                       bpt->owner->number);
> >                   fprintf_filtered (tmp_error_stream, 
> > -                                   "Error accessing memory address ");
> > +                                   " at memory address ");
> >                   fputs_filtered (paddress (bpt->address), tmp_error_stream);
> >                   fprintf_filtered (tmp_error_stream, ": %s.\n",
> >                                     safe_strerror (val));
> 
> I'm not objecting to the change, but, honestly, I don't see where
> the assumption was, or where it is being removed?

Oh, silly me.  It's the s/accessing/at/.  Ignore me there.  BTW, since
you're touching this, how about merging all those fprintf calls
into a single call, and wrapping the user visible string in _() for
translation?

-- 
Pedro Alves


  reply	other threads:[~2009-06-03 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03 20:45 Michael Snyder
2009-06-03 21:46 ` Pedro Alves
2009-06-03 22:10   ` Pedro Alves [this message]
2009-10-23 15:36   ` Michael Snyder

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=200906032311.08737.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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