> I have a simple script I sometimes run that monitors a directory for any > files dumped in it (sleeps 10 seconds, processes any new files, and loops > around). Since upgrading this script is causing bash to crash. It doesn't > happen immediately, so I'm not sure where exactly in my script this is > happening. I'll try to narrow it down more, but in the meantime I thought I > would check here for any help.
Posting the problem script would be a good start. But any crash in bash is a bug that should be identified and fixed. > Here is the stackdump: > > Exception: STATUS_ACCESS_VIOLATION at eip=61046B31 > eax=42F15F67 ebx=00000000 ecx=60030000 edx=00000000 esi=00000000 > edi=00000000 > ebp=0022E908 esp=0022E690 program=C:\cygwin\bin\bash.exe, pid 4560, thread > main > cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023 > Stack trace: > Frame Function Args > 0022E908 61046B31 (000000FF, 0022E928, 0022E924, 0043C537) Unfortunately, stackdumps on stripped binaries are pretty hard to debug. I don't know where it is crashing without something I can reproduce in a debugging binary. > begin 666 cygcheck.txt > M#0I#>6=W:[EMAIL PROTECTED])A=&EO;B!$:6%G;F]S=&EC<PT*0W5R<F5N="!3 > Problem reports: http://cygwin.com/problems.html The problem-reporting guidelines suggest plain-text (not encoded) cygcheck attachements for a reason. I can't decipher your output in my webmail reader. -- Eric Blake volunteer cygwin bash maintainer -- 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/
