Re: once more unto the breech - please try a snapshot so I can release this thing
On Sat, Jan 14, 2006 at 05:58:32PM -0800, Yitzchak Scott-Thoennes wrote: On Thu, Jan 12, 2006 at 08:35:18PM -0500, Christopher Faylor wrote: On Wed, Jan 11, 2006 at 10:46:24PM -0800, Yitzchak Scott-Thoennes wrote: Just in case it's relevant, note that I have experimental bash, readline, libreadline6, findutils, and coreutils. Does the latest snapshot behave any differently? Neither Corinna nor I can duplicate this problem so neither of us can do anything other than shoot in the dark to try to solve it. I haven't had it happen again using 20060112. I spoke too soon :(, but I wouldn't think you should hold up the release on this. -- 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/
Re: once more unto the breech - please try a snapshot so I can release this thing
On Thu, Jan 12, 2006 at 08:35:18PM -0500, Christopher Faylor wrote: On Wed, Jan 11, 2006 at 10:46:24PM -0800, Yitzchak Scott-Thoennes wrote: Just in case it's relevant, note that I have experimental bash, readline, libreadline6, findutils, and coreutils. Does the latest snapshot behave any differently? Neither Corinna nor I can duplicate this problem so neither of us can do anything other than shoot in the dark to try to solve it. I haven't had it happen again using 20060112. -- 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/
Re: once more unto the breech - please try a snapshot so I can release this thing
On Wed, Jan 11, 2006 at 10:46:24PM -0800, Yitzchak Scott-Thoennes wrote: Just in case it's relevant, note that I have experimental bash, readline, libreadline6, findutils, and coreutils. Does the latest snapshot behave any differently? Neither Corinna nor I can duplicate this problem so neither of us can do anything other than shoot in the dark to try to solve it. cgf -- 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/
Re: once more unto the breech - please try a snapshot so I can release this thing
On Jan 10, 2006, at 6:23 PM, Christopher Faylor wrote: I hope that I've nailed down the last of the problems due to trying to hide the console, aka ssh doesn't work, aka emacs doesn't work, aka rxvt doesn't work, aka setsid something doesn't work. obligatory-often-ignored-request So, please try a snapshot and report problems. Please indicate whether the problem is a regression from 1.5.18 or previous snapshots and please respond to this message when reporting a problem. Don't start a new thread. Please always provide cygcheck output even if you think you've already done it recently. Please provide exact details to duplicate a problem - a simple program indicating the problem is ideal. /obligatory-often-ignored-request It's a rather difficult bug to reproduce, but I'm still seeing the hang up with the test_configure script. I seem to be getting it about once every 2000 iterations of the program. The thread where I mentioned this problem is http://cygwin.com/ml/cygwin/2005-11/ msg0.html The script can be restarted by using the process.exe program (http:// www.beyondlogic.org/solutions/processutil/processutil.htm) using the restart option. When I run the test_configure script, after about 2000 iterations it will hang. If I do a ps -ef I can see several running sh commands from the script. I pick the one that doesn't have any children and cat /proc/pid/cmdline and it show defunct. Then I cat the winpid and use the process program to restart. This causes things to start running again. Occasionally I will see that there is a child process (i.e. sort, not another sh) If I try to cat the cmdline the cat process seems to hang; I can only kill cat with the task manager. However, I can still cat the winpid and when I do the process restart, things start running again. This behavior is fairly new. I have noted that it was the 12/22/2005 snapshot. But I didn't try the 12/21, 12/20 or 12/19 snapshots. The machine is a windows 2000 with sp4. Dual processor at 933Mhz. cygcheck.out attached. Peter cygcheck.out Description: Binary data -- 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/
Re: once more unto the breech - please try a snapshot so I can release this thing
On Jan 10, 2006, at 6:23 PM, Christopher Faylor wrote: I hope that I've nailed down the last of the problems due to trying to hide the console, aka ssh doesn't work, aka emacs doesn't work, aka rxvt doesn't work, aka setsid something doesn't work. obligatory-often-ignored-request So, please try a snapshot and report problems. Please indicate whether the problem is a regression from 1.5.18 or previous snapshots and please respond to this message when reporting a problem. Don't start a new thread. Please always provide cygcheck output even if you think you've already done it recently. Please provide exact details to duplicate a problem - a simple program indicating the problem is ideal. /obligatory-often-ignored-request It's a rather difficult bug to reproduce, but I'm still seeing the hang up with the test_configure script. I seem to be getting it about once every 2000 iterations of the program. The thread where I mentioned this problem is http://cygwin.com/ml/cygwin/2005-11/ msg0.html The script can be restarted by using the process.exe program (http:// www.beyondlogic.org/solutions/processutil/processutil.htm) using the restart option. When I run the test_configure script, after about 2000 iterations it will hang. If I do a ps -ef I can see several running sh commands from the script. I pick the one that doesn't have any children and cat /proc/pid/cmdline and it show defunct. Then I cat the winpid and use the process program to restart. This causes things to start running again. Occasionally I will see that there is a child process (i.e. sort, not another sh) If I try to cat the cmdline the cat process seems to hang; I can only kill cat with the task manager. However, I can still cat the winpid and when I do the process restart, things start running again. This behavior is fairly new. I have noted that it was the 12/22/2005 snapshot. But I didn't try the 12/21, 12/20 or 12/19 snapshots. The machine is a windows 2000 with sp4. Dual processor at 933Mhz. cygcheck.out attached. Peter (this is a resend...the first one seems to have disappeared) cygcheck.out Description: Binary data -- 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/
Re: once more unto the breech - please try a snapshot so I can release this thing
On Wed, Jan 11, 2006 at 10:35:37AM -0800, Yitzchak Scott-Thoennes wrote: On Tue, Jan 10, 2006 at 09:23:41PM -0500, Christopher Faylor wrote: I hope that I've nailed down the last of the problems due to trying to hide the console, aka ssh doesn't work, aka emacs doesn't work, aka rxvt doesn't work, aka setsid something doesn't work. :( emacs doesn't work. Twice now with the 20060110 13:32:19 snapshot, I've had it no longer receive Ctrl-C's (running emacs from mutt from a cygwin.bat window). Doesn't happen consistently, but when it does, it persists in any emacs started in that window. When I finally exit bash, cmd.exe gives a Terminate batch job (Y/N)? prompt. Probably useless information: I had something similar happen once with, I think, the 20060105 snapshot, but then cygwin1.dll showed some error message (TM) about a minute after Ctrl-C was pressed. I notice that you included the part of my message where I say what I think I fixed but didn't include the part where I mentioned that we need to know the steps to duplicate the problem. What *exactly* are you doing? I think it's been mentioned a few times that neither Corinna nor I use emacs so running emacs from mutt doesn't mean a lot to me and it probably doesn't mean much to the only other person who's going to be interested in tracking down this problem. cgf -- 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/
Re: once more unto the breech - please try a snapshot so I can release this thing
On Wed, Jan 11, 2006 at 08:17:08PM -0500, Christopher Faylor wrote: On Wed, Jan 11, 2006 at 10:35:37AM -0800, Yitzchak Scott-Thoennes wrote: On Tue, Jan 10, 2006 at 09:23:41PM -0500, Christopher Faylor wrote: I hope that I've nailed down the last of the problems due to trying to hide the console, aka ssh doesn't work, aka emacs doesn't work, aka rxvt doesn't work, aka setsid something doesn't work. :( emacs doesn't work. Twice now with the 20060110 13:32:19 snapshot, I've had it no longer receive Ctrl-C's (running emacs from mutt from a cygwin.bat window). Doesn't happen consistently, but when it does, it persists in any emacs started in that window. When I finally exit bash, cmd.exe gives a Terminate batch job (Y/N)? prompt. Probably useless information: I had something similar happen once with, I think, the 20060105 snapshot, but then cygwin1.dll showed some error message (TM) about a minute after Ctrl-C was pressed. I notice that you included the part of my message where I say what I think I fixed but didn't include the part where I mentioned that we need to know the steps to duplicate the problem. What *exactly* are you doing? I think it's been mentioned a few times that neither Corinna nor I use emacs so running emacs from mutt doesn't mean a lot to me and it probably doesn't mean much to the only other person who's going to be interested in tracking down this problem. Usually using mutt's g command to reply to an email, which starts e.g. emacs -nw /tmp/mutt-DHX98431-3796-19 to edit an email. And when I've finished editing, I use the Ctrl-X Ctrl-C command to exit, and sometimes the Ctrl-X is registered but the Ctrl-C is ignored. And sometimes it works. What the difference is, I don't know. I've had it happen one more time, and still have the window open. Just now, I tried entering sleep 20 at the bash prompt in that window and right thereafter Ctrl-C and the sleep wasn't interrupted. Sorry I can't tell you what makes this happen or not happen. -- 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/
Re: once more unto the breech - please try a snapshot so I can release this thing
On Wed, Jan 11, 2006 at 10:41:20PM -0800, Yitzchak Scott-Thoennes wrote: On Wed, Jan 11, 2006 at 08:17:08PM -0500, Christopher Faylor wrote: On Wed, Jan 11, 2006 at 10:35:37AM -0800, Yitzchak Scott-Thoennes wrote: On Tue, Jan 10, 2006 at 09:23:41PM -0500, Christopher Faylor wrote: I hope that I've nailed down the last of the problems due to trying to hide the console, aka ssh doesn't work, aka emacs doesn't work, aka rxvt doesn't work, aka setsid something doesn't work. :( emacs doesn't work. Twice now with the 20060110 13:32:19 snapshot, I've had it no longer receive Ctrl-C's (running emacs from mutt from a cygwin.bat window). Doesn't happen consistently, but when it does, it persists in any emacs started in that window. When I finally exit bash, cmd.exe gives a Terminate batch job (Y/N)? prompt. Probably useless information: I had something similar happen once with, I think, the 20060105 snapshot, but then cygwin1.dll showed some error message (TM) about a minute after Ctrl-C was pressed. I notice that you included the part of my message where I say what I think I fixed but didn't include the part where I mentioned that we need to know the steps to duplicate the problem. What *exactly* are you doing? I think it's been mentioned a few times that neither Corinna nor I use emacs so running emacs from mutt doesn't mean a lot to me and it probably doesn't mean much to the only other person who's going to be interested in tracking down this problem. Usually using mutt's g command to reply to an email, which starts e.g. emacs -nw /tmp/mutt-DHX98431-3796-19 to edit an email. And when I've finished editing, I use the Ctrl-X Ctrl-C command to exit, and sometimes the Ctrl-X is registered but the Ctrl-C is ignored. And sometimes it works. What the difference is, I don't know. I've had it happen one more time, and still have the window open. Just now, I tried entering sleep 20 at the bash prompt in that window and right thereafter Ctrl-C and the sleep wasn't interrupted. Sorry I can't tell you what makes this happen or not happen. Just in case it's relevant, note that I have experimental bash, readline, libreadline6, findutils, and coreutils. -- 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/
once more unto the breech - please try a snapshot so I can release this thing
I hope that I've nailed down the last of the problems due to trying to hide the console, aka ssh doesn't work, aka emacs doesn't work, aka rxvt doesn't work, aka setsid something doesn't work. obligatory-often-ignored-request So, please try a snapshot and report problems. Please indicate whether the problem is a regression from 1.5.18 or previous snapshots and please respond to this message when reporting a problem. Don't start a new thread. Please always provide cygcheck output even if you think you've already done it recently. Please provide exact details to duplicate a problem - a simple program indicating the problem is ideal. /obligatory-often-ignored-request Failure to provide any of the above in a report will result in taunting and/or mocking. You have been warned. Oh. And, fixes are always welcome. cgf -- 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/