Hi I sent the posting below to the list once, but apparently it was blocked. Here it is again. ("test.bat" renamed to see if that will get the message through..)
Pointers, hints or help all graciously accepted :-). -----Forwarded Message----- Anybody have any idea how to pursue the bug quoted at the bottom? A few other bugs has occurred with 20050221, nothing serious though: 1. 'grep' returns exit code 0 as in "found", but doesn't echo the found line to stdout. And in fact, the string that was being grepped for doesn't exist in the input, so the exit code (0) is an error. It's a bit hard to reproduce (same as the quoted bug) so far, but it seems to happen quite often.. 2. 'grep' occasionally returns error 139. This one is very easy to reproduce - let the attached script run for a couple of hours and see the output file. Not sure if this is a bug or not? What does error code 139 mean? 3. This has occurred once in a running script. Something similar often happens when CTRL-C is pressed in an interactive shell running some program. I haven't been able to reproduce it outside of the interactive shell yet. 1488 [main] bash 4428 sync_with_child: child 3276(0x118) died before initialization with status code 0x80 30328 [main] bash 4428 sync_with_child: *** child state waiting for longjmp agent.sh: fork: Resource temporarily unavailable David Dindorp wrote: > So far a couple of things have popped up in testing. Only one of them > is a new item since I started using the 20050221 snapshot. It has > occurred 2 times over 2 days so far,so I feel that it is reproducible. > > Bash hangs. Both occurrences have been at the same specific script > line, and both produce similar gdb output. > > Script line: > lffields[$counter]=`echo $lfline|cut -d'|' -f$fieldno` > > Script line - process 592: > +++ echo '0007-02-2005-01-29-22-15-24-xferslowevlog.log|0|1107034112|1107034112|1 107034675|1107035470' > +++ cut '-d|' -f5 > > Script line - process 3164: > +++ echo '0007-02-2005-02-10-06-02-55-xferslowevlog.log|0|1108012113|-1|110801244 7|1108012465' > +++ cut '-d|' -f1 > > Backtrace, dumped process 592: > #0 0x77f8a1eb in ntdll!ZwSetInformationThread () > #1 0x7c4fb5bf in SetThreadPriority () > #2 0x610035c6 in getprogname () > #3 0x6105ad27 in cygwin_split_path () > #4 0x61019478 in cygwin_internal () > #5 0x6107bc25 in getppid () > #6 0x6107ba4d in getppid () > #7 0x610723ff in cygwin1!aclcheck () > #8 0x0042562a in ?? () > #9 0x00000005 in ?? () > #10 0x0022cf20 in ?? () > #11 0x00000080 in ?? () > #12 0x610749bb in writev () > > Backtrace, dumped process 3163: > #0 0x77f8a1eb in ntdll!ZwSetInformationThread () > #1 0x7c4fb5bf in SetThreadPriority () > #2 0x610035c6 in getprogname () > #3 0x6105ad27 in cygwin_split_path () > #4 0x61019478 in cygwin_internal () > #5 0x6107bc25 in getppid () > #6 0x6107ba4d in getppid () > #7 0x610723ff in cygwin1!aclcheck () > #8 0x0042562a in ?? () > #9 0x00000005 in ?? () > #10 0x0022cf20 in ?? () > #11 0x00000080 in ?? () > #12 0x610749bb in writev () > > > (I'm obviously a n00b with gdb. The similar output could be a > side effect from debugging the processes?..)
test.sh
Description: test.sh
test.tab
Description: test.tab
-- 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/