On Sep 16 13:31, Hommersom, Fred wrote: > No problem. here is a new trace (similar to the original) and the related > stackdump > > Exception: STATUS_ACCESS_VIOLATION at eip=610D6971 > eax=00000000 ebx=10010248 ecx=FFFFF2FF edx=00245300 esi=00000001 edi=00246000 > ebp=0022EE68 esp=0022EE64 program=c:\cygwin\bin\bash.exe, pid 3572, thread > main > cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 > Stack trace: > Frame Function Args > 0022EE68 610D6971 (00245300, 00000040, 6110E714, 6110E77B) > 0022EEE8 6105390B (00000000, 00000000, 0022EF18, 61090062) > 0022EF18 6106EFC8 (00000000, 00000000, 7C90E64E, 77DDDB0D) > 0022EFC8 61004D1D (0022EFE0, 00000000, 0022EFC0, 77D4A303) > 0022FF88 61005B6F (00000000, 00000000, 00000000, 00000000) > End of stack trace > Sure you've used the latest snapshot DLL? I tried to reproduce this with the latest snapshot, as well as a self-build DLL from CVS and I can't reproduce this behaviour. My test environment consisted of 1400 variables with a size of 98K, one of the variables taking roughly 31K alone. However, what's strange in your strace output is this:
> 442 785 [main] bash 3504 environ_init: 0x10010238: X$ > 37 822 [main] bash 3504 environ_init: 0x10010248: ðH$ > 97 919 [main] bash 3504 handle_exceptions: In cygwin_except_handler > exc 0xC0000005 at 0x610D6971 sp 0x22EE64 The first two lines should contain some valid environment entries, but both of them look broken. There's no hint why this is, of course. I observerd that tcsh doesn't like variables with a length of 31K, though. ash, bash, zsh and pdksh could handle that long environment varibale just fine, tcsh on the other hand printed this: $ echo $VERY_LONG_ENV_VAR Word too long. Sigh, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
