Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb-patches@sourceware.org
Subject: Re: [New WinCE support] [patch 4/4] The bulk of the code.
Date: Mon, 19 Mar 2007 04:21:00 -0000	[thread overview]
Message-ID: <uslc16eyq.fsf@gnu.org> (raw)
In-Reply-To: <45FDE45F.2000309@portugalmail.pt> (message from Pedro Alves on 	Mon, 19 Mar 2007 01:16:15 +0000)

> Date: Mon, 19 Mar 2007 01:16:15 +0000
> From: Pedro Alves <pedro_alves@portugalmail.pt>
> CC:  gdb-patches@sourceware.org
> 
> > Btw, I see in your patch two instances of strwinerror and two places
> > that call it: one in gdbreplay.c, the other in utils.c.  Why did you
> > need two almost identical functions?
> 
> Well, gdbreplay (a separate application) has some other functionality
> that is copied from gdbserver instead of sharing objects,
> eg: perror_with_name.  I didn't think it was worth it to change
> how it is built for just one function.

Sounds rather unclean to me, but if no one else cares, I won't insist.

> They are not identical, because the gdbserver version only
> cares about UNICODE (Win32 API on Windows CE is only wide).

I saw that (that's why I said ``almost identical''), but the
difference is still very minor, so that a version that suits both
types of usage could be easily written.

> >> The errno values and the windows error codes are not the same.
> >
> > This is not a problem: errno should not be used with any literal
> > values anyway, only with symbolical constants.
> 
> I don't understand what you mean here.

I mean that, since WinCE doesn't have errno.h, you could define error
symbols such as EINTR and EMFILE as appropriate for values returned by
GetLastError.

Thanks for the new patch, I'm happy now.


  reply	other threads:[~2007-03-19  4:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070315235008.243411000@portugalmail.pt>
2007-03-16  2:07 ` [New WinCE support] [patch 1/4] : mv win32-i386-low.c win32-low.c Pedro Alves
2007-03-27 19:11   ` Daniel Jacobowitz
2007-03-16  2:09 ` [New WinCE support] [patch 2/4] : s/thread_info/win32_thread_info/g Pedro Alves
2007-03-27 19:12   ` Daniel Jacobowitz
2007-03-16  2:09 ` [New WinCE support] [patch 3/4] : bfd config Pedro Alves
2007-03-16  2:10 ` [New WinCE support] [patch 4/4] The bulk of the code Pedro Alves
2007-03-16 12:52   ` Eli Zaretskii
2007-03-16 15:03     ` pedro alves
2007-03-17 11:18       ` Eli Zaretskii
2007-03-17 11:35         ` Andreas Schwab
2007-03-19  1:53         ` Pedro Alves
2007-03-19  4:21           ` Eli Zaretskii [this message]
2007-03-19 12:34             ` Daniel Jacobowitz
2007-03-27 19:20           ` Daniel Jacobowitz
2007-03-29  3:18             ` Pedro Alves
2007-03-29  3:51             ` Pedro Alves
2007-03-30 11:56               ` Pierre Muller
2007-03-30 12:23                 ` pedro alves
2007-03-30 20:35                   ` pedro alves

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=uslc16eyq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro_alves@portugalmail.pt \
    /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