This is the mail archive of the 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]

Re: Broken since 1.3.10, or earlier


Wednesday, 17 July, 2002 Christopher Faylor wrote:

CF> On Tue, Jul 16, 2002 at 05:00:38PM -0700, Randall R Schulz wrote:
>>Someone who knows about the internal architecture of I/O processing in 
>>Cygwin might be able to shed some light on this. If, for example, there's 
>>some kind of queuing of I/O operations in Cygwin1.dll between the 
>>application code (grep or a shell, in this case) and the Windows I/O 
>>primitives, then there might be an opportunity for this kind of asynchrony.

Seen this too.

CF> Actually, AFAICT, it is a bash bug and one that I have reported earlier.

CF> bash makes assumptions that pids grow monotonically but that is not the
CF> case on windows.

But that can't be the case on any unix too! Sooner or later system
reach maximum possible value of pid and will have to turn it over. Can
you point where bash makes such assumptions, and probably this can be
fixed in bash?

Egor.   ICQ 5165414 FidoNet 2:5020/496.19

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]