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

2005-09-19 Thread Hommersom, Fred
Thanks for the answer. Fred >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 enviro

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

2005-09-16 Thread Hommersom, Fred
>>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 ** Here are the results of the test below the maximum ***

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

2005-09-16 Thread Hommersom, Fred
Perhaps I do not understand it. I was talking about invoking cygin from native. The native environment grows far over 32 k. It just does not show up in bash. If I can help by testing the new snapshot: please supply some hints. Fred >On the other hand, POSIX would claim that this usage should b

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

2005-09-16 Thread Hommersom, Fred
> > From your strace output, it looks to me like windows itself is returning garbage when we ask it for the list of environment variables. > >If that is the case, we can guard against that but we can't make the passed in environment useful, unfortunately. Is it possible that 'asking for the envi

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

2005-09-16 Thread Hommersom, Fred
Yes sure. You can see this in the header of the dump its says: DLL version: 1005.19, api: 0.138 DLL build:20050916 00:00:39SNP In order to be sure that we are talking about the same things: I have all these variables in DOS and start bash from a CMD window with command c:\cygwin\bin\strace -o

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

2005-09-16 Thread Hommersom, Fred
No problem. here is a new trace (similar to the original) and the related stackdump Exception: STATUS_ACCESS_VIOLATION at eip=610D6971 eax= ebx=10010248 ecx=F2FF edx=00245300 esi=0001 edi=00246000 ebp=0022EE68 esp=0022EE64 program=c:\cygwin\bin\bash.exe, pid 3572, thread main cs=0

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

2005-09-16 Thread Hommersom, Fred
0x8B, exitcode 0x0 -Original Message- On Sep 16 11:08, Hommersom, Fred wrote: > > Thanks for the replies so far. Unfortunately is the best option (set > variables in bash) not feasable. > The .bat file is a complex set of bat files with logic inside so that > would take a

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

2005-09-16 Thread Hommersom, Fred
o exact match. Now I am stuck. Did I reach a limit of windoze, a limit in cygwin or a supporting library or a bug? -Original Message- > Hommersom, Fred wrote: > >> >> The file bigsetup.bat contains a huge amount environment variables. >> For a medium number

Bash login breaks if too many environment variables are set

2005-09-12 Thread Hommersom, Fred
My startup of cygwin is a .bat file with contents call bigsetup.bat set HOME=C:\Data\locations\tc50_custy00 c:\cygwin\bin\bash --login -i The file bigsetup.bat contains a huge amount environment variables. For a medium number (~ 600) everything works fine For a larger number the output is: bash