Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Darwin/x86 port (v3 of part 3: i386-darwin files)
Date: Fri, 14 Nov 2008 15:32:00 -0000	[thread overview]
Message-ID: <uwsf6o8se.fsf@gnu.org> (raw)
In-Reply-To: <20081112125150.GA21514@ulanbator.act-europe.fr>

> Date: Wed, 12 Nov 2008 13:51:50 +0100
> From: Tristan Gingold <gingold@adacore.com>
> 
> i386-darwin-tdep.h:

Thanks.

> /* Offsets into the struct i386_thread_state where we'll find the saved regs. */
> /* From <mach/i386/thread_status.h and i386-tdep.h */
                                    ^
A closing bracket `>' is missing here.

> /* Offsets into the struct x86_thread_state64 where we'll find the saved regs. */
> /* From <mach/i386/thread_status.h and amd64-tdep.h */
                                    ^
And here.

> 	  if (ret != KERN_SUCCESS)
> 	    {
> 	      printf ("Error calling thread_get_state for GP registers for thread 0x%ulx", current_thread);
> 	      MACH_CHECK_ERROR (ret);

printf? is that right? didn't you mean printf_filtered or
printf_unfiltered?

In any case, please enclose all user messages in _(), for when we will
support l10n.

(There are several similar instances elsewhere in this patch.)

>   if (! fetched)
>     {
>       warning ("unknown register %d", regno);

Same here: please use _().


      parent reply	other threads:[~2008-11-14 11:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-13 18:34 Tristan Gingold
2008-11-12 19:10 ` Tristan Gingold
2008-11-13 14:48 ` Tristan Gingold
2008-11-14 15:32 ` Eli Zaretskii [this message]

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=uwsf6o8se.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.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