This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Sometimes, sed (when called from our own modified zsh in sh mode) gives this assertion: assertion "!wait_sig_inited" failed: file "/netrel/src/cygwin-1.3.17-1/winsup/cy gwin/sigproc.cc", line 538 repeatedly and then: 159 [main] sed 3464 sig_send: wait for sig_complete event failed, sig nal -2, rc 258, Win32 error 0 68138 [sig] sed 3464 sig_send: wait for sig_complete event failed, signal 6, r c 258, Win32 error 0 (I assume this means it's sed asserting?) There doesn't seem to be a pattern as to when this happens. Sorry I couldn't provide a test case but hopefully this is helpful. I have since downgraded to the 3.0.2-1 version which explains the descepency in cygcheck.out. When I was using cygwin 1.13.14-1 (and I imagine 3.0.2-1 of sed) I didn't get this problem. Andrew
Attachment:
cygcheck.out
Description: Binary data
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |