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: Fri, 16 Mar 2007 12:52:00 -0000 [thread overview]
Message-ID: <uy7lxnydu.fsf@gnu.org> (raw)
In-Reply-To: <45F9FC33.9020106@portugalmail.pt> (message from Pedro Alves on Fri, 16 Mar 2007 02:08:51 +0000)
> Date: Fri, 16 Mar 2007 02:08:51 +0000
> From: Pedro Alves <pedro_alves@portugalmail.pt>
>
> This patch is the bulk of the new WinCE support.
Thanks.
I have a few comments.
> +static char *
> +strwinerror (DWORD error)
> +{
> + static char buf[1024];
> + wchar_t msgbuf[1024];
> + DWORD chars = FormatMessageW (
> + FORMAT_MESSAGE_FROM_SYSTEM,
> + NULL,
> + error,
> + 0, /* Default language */
> + (LPVOID)&msgbuf,
> + 0,
> + NULL);
Instead of using an arbitrary size 1024 (btw, you don't check whether
FormatMessageW indicated that it needed more than 1024), isn't it
better to use FORMAT_MESSAGE_ALLOCATE_BUFFER? As a bonus, it would
avoid overwriting the static buffer on each call, which is not a nice
API, IMHO.
> +#ifdef __MINGW32CE__
> + err = strwinerror (GetLastError ());
> +#else
> err = strerror (errno);
> +#endif
Why not call strwinerror strerror and avoid the ifdef?
> doc/ChangeLog
>
> * gdb.texinfo (WinCE): Delete subsection.
Why? Is that subsection incorrect in some ways?
next prev parent reply other threads:[~2007-03-16 12:52 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 [this message]
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
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=uy7lxnydu.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