From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFA] windows-nat.c: Cygwin: Port to Cygwin 1.7
Date: Sun, 28 Feb 2010 17:49:00 -0000 [thread overview]
Message-ID: <83wrxxb690.fsf@gnu.org> (raw)
In-Reply-To: <20100228171828.GK5683@calimero.vinschen.de>
> Date: Sun, 28 Feb 2010 18:18:28 +0100
> From: Corinna Vinschen <vinschen@redhat.com>
>
> On Feb 28 19:08, Eli Zaretskii wrote:
> > > Date: Sun, 28 Feb 2010 16:08:44 +0100
> > > From: Corinna Vinschen <vinschen@redhat.com>
> > >
> > > - 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.
> >
> > I'd suggest not to introduce arbitrary limits. If we are going to use
> > the Unicode APIs, let's support the full 32K length they give us.
>
> Some buffers are on the stack and would have an unnecessary big size.
I don't think 32K is too much for the Windows stack (but maybe it is
with Cygwin; I don't know enough to judge). In Emacs, we had until a
month ago code that used alloca to allocate a 700KB structure, and it
worked in the native Windows build without any problems.
> PATH_MAX, 4K, is more than enough especially since the names of DLLs
> are stored in a buffer which is restricted to SO_NAME_MAX_PATH_SIZE,
> which is 512 bytes ATM.
I wasn't thinking about DLL names, I was thinking about source file
names and names of executable programs.
next prev parent reply other threads:[~2010-02-28 17:49 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 [this message]
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
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=83wrxxb690.fsf@gnu.org \
--to=eliz@gnu.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