[Fwd: [que_andrewBOOHyahoo.com: FOLLOWUP: 1.5.12: problems without registry keys]]

2004-12-13 Thread Corinna Vinschen
Pierre, I think I tracked the problem down, reported in http://cygwin.com/ml/cygwin/2004-12/msg00236.html I'm asking you since you were the one introducing cwdstuff->get_drive(). I found that the problem was raised by just using threads, nothing to do with Semaphores, and only if a thread a

Re: [Fwd: [que_andrewBOOHyahoo.com: FOLLOWUP: 1.5.12: problems without registry keys]]

2004-12-13 Thread Pierre A. Humblet
Corinna Vinschen wrote: > Is that ok to apply or is there any good reason not to release the muto > when get_drive() has finished? I can't see any, FWIW. Oops, please apply ASAP of course. Pierre

Re: [Fwd: [que_andrewBOOHyahoo.com: FOLLOWUP: 1.5.12: problems without registry keys]]

2004-12-13 Thread Christopher Faylor
On Mon, Dec 13, 2004 at 01:31:58PM -0500, Pierre A. Humblet wrote: >Corinna Vinschen wrote: >> Is that ok to apply or is there any good reason not to release the muto >> when get_drive() has finished? I can't see any, FWIW. > >Oops, please apply ASAP of course. Sounds like I should release 1.5.13

Re: [Patch] Fixing the PROCESS_DUP_HANDLE security hole.

2004-12-13 Thread Christopher Faylor
With the current CVS, I am seeing the same (suboptimal) behavior on Windows Me that I do in 1.5.12. If I type a bunch of "sleep 60&" at the command line, then "bash" won't exit until the last sleep 60 has terminated. I can't explain why this is. It doesn't work that way on XP, of course. While

Re: [Fwd: [que_andrewBOOHyahoo.com: FOLLOWUP: 1.5.12: problems without registry keys]]

2004-12-13 Thread Corinna Vinschen
On Dec 13 13:31, Pierre A. Humblet wrote: > Corinna Vinschen wrote: > > Is that ok to apply or is there any good reason not to release the muto > > when get_drive() has finished? I can't see any, FWIW. > > Oops, please apply ASAP of course. Ok, done. Thanks, Corinna -- Corinna Vinschen

Re: [Fwd: [que_andrewBOOHyahoo.com: FOLLOWUP: 1.5.12: problems without registry keys]]

2004-12-13 Thread Reini Urban
Christopher Faylor schrieb: On Mon, Dec 13, 2004 at 01:31:58PM -0500, Pierre A. Humblet wrote: Corinna Vinschen wrote: Is that ok to apply or is there any good reason not to release the muto when get_drive() has finished? I can't see any, FWIW. Oops, please apply ASAP of course. Sounds like I shou

Re: change log fix: [Patch] bug # 514 (cygwin console handling)

2004-12-13 Thread Corinna Vinschen
On Dec 1 08:16, Thomas Wolff wrote: > Sorry, I missed to insert the function name in the change log > entry, so here it is again as an update; the patch is the same. > > This is a small patch that fixes > http://sourceware.org/bugzilla/show_bug.cgi?id=514 > > Please integrate it into the cygwi

Re: [Patch] bug # 512 (cygwin console handling)

2004-12-13 Thread Corinna Vinschen
On Nov 30 22:31, Thomas Wolff wrote: > This is a small patch that fixes > http://sourceware.org/bugzilla/show_bug.cgi?id=512 > > Please integrate it into the cygwin DLL. > > 2004-11-26 Thomas Wolff <[EMAIL PROTECTED]> > > * fhandler_console.cc (read) : > Considering offset within scroll

Re: [Patch] Fixing the PROCESS_DUP_HANDLE security hole.

2004-12-13 Thread Pierre A. Humblet
Christopher Faylor wrote: > > With the current CVS, I am seeing the same (suboptimal) behavior on > Windows Me that I do in 1.5.12. > > If I type a bunch of "sleep 60&" at the command line, then "bash" won't > exit until the last sleep 60 has terminated. I can't explain why this > is. It doesn