RE: 1.5.11: resuming a suspended sleep results in undelivered signal 19

2004-09-19 Thread Bogdan Vacaliuc
> It is actually more likely a tie in with: > > http://sources.redhat.com/ml/cygwin/2004-09/msg00315.html Yah! Light years away... :) > This problem should be fixed in the latest snapshot. Indeed, it is. Many thanks! -bogdan -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simp

1.5.11: resuming a suspended sleep results in undelivered signal 19

2004-09-19 Thread Bogdan Vacaliuc
Greetings, Pierre Humblet discovered this and since I had a trace of it, encouraged me to post it. A suspended sleep call is resumed, but does not exit at the expiration time. $ sleep 20 ^Z [1]+ Stopped sleep 20 $ fg sleep 20 ...forever... In a separate shell, the sleep is str

RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)

2004-09-15 Thread Bogdan Vacaliuc
Chris, My local tests and all reports from rtems-users so far are successes. -bogdan > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Peter Ekberg > Sent: Wednesday, September 15, 2004 3:24 AM > To: [EMAIL PROTECTED] > Subject: RE: 1.5.10: expr +

RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)

2004-09-14 Thread Bogdan Vacaliuc
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Pierre A. Humblet > Sent: Tuesday, September 14, 2004 10:04 AM > To: [EMAIL PROTECTED] > Subject: Re: 1.5.10: expr + configure failure + testcase > (also on 1.5.11-1) > > > On

RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)

2004-09-14 Thread Bogdan Vacaliuc
Chris, Ok. Running 09/14/04 snapshot is looking *good* so far. I stopped the test script at 150 passes. I'm starting my configure/build/redo test and will let that run overnight. I'll check in tomorrow AM and report on that. 1 successful configure/build so far. Thanks! -bogdan -- Unsubs

RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)

2004-09-14 Thread Bogdan Vacaliuc
Hi Peter, > Yes, the new trace is with cygwin1.dll 1.5.11-1, the old one > was with 1.5.10-3, sorry if I didn't mention that... No, that's fine. It would have been significant if you *had not* upgraded and yet produced that failure. -bogdan -- Unsubscribe info: http://cygwin.com/ml/#un

RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)

2004-09-13 Thread Bogdan Vacaliuc
Chris, Pierre, > I was thinking the same thing but AFAIK, ash doesn't have the > pid recycling problem. In my failure cases, configure is run under bash. I have also captured (finally?) an strace under the ~current cygwin (attached). The details are largely the same as Peter's last attachment

RE: HELP: How to disable killing of Bash Shell window with mouse?

2004-09-13 Thread Bogdan Vacaliuc
Hi Pekka, http://www.google.com/search?hl=en&lr=&ie=UTF-8&q=%2Bdisable+%2Bclose+%2Bwindow The first hit is: http://www.handyarchive.com/Desktop/Shell-Enhancements/4-WinTopMost-Site-License.html Which is a link to a commercial product, but perhaps it will satisfy you or perhaps more searchi

RE: 1.5.10: expr + configure failure + testcase (also on 1.5.11-1)

2004-09-12 Thread Bogdan Vacaliuc
Hello again, After (finally?!) noticing that a new release of the cygwin.dll was made on Sept. 4 and being encouraged by the line: "- Fix mysterious configure script premature exit. (Pierre Humblet)" I decided to check against the latest public release. The problem continues to persist, unfo

RE: 1.5.10: expr + configure failure + testcase

2004-09-11 Thread Bogdan Vacaliuc
Excuse me. Please perform the following on the script: $ sed -i '1 s/\/sh/\/bash/' test-drive I attach an archive with the updated script. -bogdan begin 666 configure-test.tar.bz2 M0EIH.3%!62936=4"F0T`,A1_I/__>0!___\!`0``@ [EMAIL PROTECTED]/X[ MN?3"^;--%\/7GN??;E7OICRO4JLJTH%F4:)V

1.5.10: expr + configure failure + testcase

2004-09-11 Thread Bogdan Vacaliuc
Greetings, The RTEMS project has also experienced the configure/expr problem over the last few weeks. A number of people have been working on it, and I would like to present our findings as well as offer a test case that exposes the problem fairly readily. As Igor has deduced in (http://sources.