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 ********************************************** Program name: c:\cygwin\bin\bash.exe (pid 3504, ppid 1) App version: 1005.18, api: 0.132 DLL version: 1005.19, api: 0.138 DLL build: 20050916 00:00:39SNP OS version: Windows NT-5.1 Heap size: 1073741824 Date/Time: 2005-09-16 13:29:23 ********************************************** 27 319 [main] bash 3504 set_myself: myself->dwProcessId 3504 24 343 [main] bash 3504 time: 1126870163 = time (0) 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 24 943 [main] bash 3504 handle_exceptions: In cygwin_except_handler sig 11 at 0x610D6971 77 1020 [main] bash 3504 handle_exceptions: In cygwin_except_handler calling 0x0 23 1043 [main] bash 3504 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION 353 1396 [main] bash 3504 try_to_debug: debugger_command '' 519 1915 [main] bash 3504 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump 861081 862996 [main] bash 3504 signal_exit: about to call do_exit (8B) 81 863077 [main] bash 3504 do_exit: do_exit (139), exit_state 0 67 863144 [main] bash 3504 void: 0x0 = signal (20, 0x1) 59 863203 [main] bash 3504 void: 0x0 = signal (1, 0x1) 55 863258 [main] bash 3504 void: 0x0 = signal (2, 0x1) 55 863313 [main] bash 3504 void: 0x0 = signal (3, 0x1) 79 863392 [main] bash 3504 sigproc_terminate: entering 59 863451 [main] bash 3504 sig_send: my_sendsig 0x0, myself->sendsig 0x0, exit_state 9 58 863509 [main] bash 3504 __set_errno: int sig_send(_pinfo*, siginfo_t&, _cygtls*):548 val 11 59 863568 [main] bash 3504 sig_send: returning 0x1 from sending signal -42 57 863625 [main] bash 3504 proc_terminate: nprocs 0 56 863681 [main] bash 3504 proc_terminate: leaving 95 863776 [main] bash 3504 sigproc_terminate: already performed 59 863835 [main] bash 3504 __to_clock_t: dwHighDateTime 0, dwLowDateTime 0 57 863892 [main] bash 3504 __to_clock_t: total 00000000 00000000 58 863950 [main] bash 3504 __to_clock_t: dwHighDateTime 0, dwLowDateTime 200288 57 864007 [main] bash 3504 __to_clock_t: total 00000000 00000014 912 864919 [main] bash 3504 pinfo::maybe_set_exit_code_from_windows: pid 3504, exit value - old 0x800008B, windows 0xDEADBEEF, cygwin 0x800008B 156 865075 [main] bash 3504 pinfo::exit: Calling ExitThread hProcess 0x0, n 0x8B, exitcode 0x0 -----Original Message----- > The problem can be reproduced with cygwin1-20050916.dll >> >>Sorry, I forgot to mention, can you please add the stackdump, too? -- 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/