Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] windows-nat.c: Cygwin: Port to Cygwin 1.7
Date: Sun, 28 Feb 2010 22:30:00 -0000	[thread overview]
Message-ID: <20100228223046.GD29104@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20100228150844.GH5683@calimero.vinschen.de>

On Sun, Feb 28, 2010 at 04:08:44PM +0100, Corinna Vinschen wrote:
>Hi,
>
>the below patch ports GDB to the latest Cygwin version 1.7.
>
>Three problems have to be fixed:
>
>- The maximum path length in Cygwin is no longer MAX_PATH.  Rather it
>  is PATH_MAX, which is now 4096.  Actually, even paths up to 32K are
>  supported, which is the maximum path length of the underlying Windows,
>  but usually 4K is more than enough.
>
>- The aforementioned change required to provide a new Win32<->POSIX
>  path conversion API which allows to handle paths longer than MAX_PATH.
>  The old cygwin_conv_to_[full_]win32_path and cygwin_conf_to_[full_]posix
>  path functions are deprecated now.  The below patch uses the new
>  cygwin_conv_path API instead.
>
>- The Windows ANSI functions have two drawbacks.
>
>  - They return paths always in the default ANSI codepage, which is
>    typically not the default codeset used in Cygwin 1.7 anymore.  UTF-8
>    is now the default codeset in Cygwin.
>
>  - They are restricted to a path length of MAX_PATH bytes.
>
>  Since UTF-8 support and support for long paths are key changes in
>  Cygwin 1.7, Cygwin now uses only Unicode Windows or native NT
>  functions internally.  To overcome the restrictions of the Win32 ANSI
>  functions in GDB as well, the patch changes the affected calls to use
>  the Unicode variation instead, too.
>
>The code for other Win32 targets is unaffected by this patch, except
>for a patch in get_image_name.  The WideCharToMultiByte function is
>called with an incorrect target buffer size.
>
>Ok to apply?

They look reasonable.  I've had less comprehensive changes sitting in my
sandbox for a while.  Please apply.

cgf


  parent reply	other threads:[~2010-02-28 22:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28 15:09 Corinna Vinschen
2010-02-28 16:56 ` Pierre Muller
2010-02-28 17:09   ` Corinna Vinschen
2010-02-28 17:08 ` Eli Zaretskii
2010-02-28 17:18   ` Corinna Vinschen
2010-02-28 17:49     ` Eli Zaretskii
2010-02-28 18:01       ` Corinna Vinschen
2010-02-28 18:56         ` Eli Zaretskii
2010-02-28 19:24           ` Corinna Vinschen
2010-02-28 22:30 ` Christopher Faylor [this message]
2010-03-01  9:10   ` Corinna Vinschen
2010-03-01 10:04 Roland Schwingel
2010-03-01 15:23 ` Christopher Faylor

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=20100228223046.GD29104@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    /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