This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bash login breaks if too many environment variables are set

On Sep 16 21:55, Hommersom, Fred wrote:
> >>You can help by running the new snapshot under strace, like you did before.
> I have done three tests:
> below the maximum
> exactly the maximum
> over the maximum

Further empirical tests turned out that the environment in Windows NT
is not limited, at least not up to a tested size of about 800K.

But there is a big problem in Windows nevertheless.  When using ASCII
functions to access the environment, as Cygwin does, the environment
is silently cut off at 32K.  There's no error message or any hint
in the documentation that something like this would happen when trying
to retrieve the environment.  Trying to start another process with
an ASCII environment > 32K results in an error code returned by
CreateProcess.  So, for now you have to live with an environment < 32K.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat, Inc.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]