delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/05/28/18:51:54

X-Spam-Check-By: sourceware.org
Date: Sun, 28 May 2006 18:51:47 -0400 (EDT)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: cygwin1-20060527: replicated stdout (Was Re: cygwin1-20060519: proc_waiter: unknown value * on proc pipe)
In-Reply-To: <Pine.GSO.4.63.0605192221450.16587@access1.cims.nyu.edu>
Message-ID: <Pine.GSO.4.63.0605281831130.19906@access1.cims.nyu.edu>
References: <Pine DOT GSO DOT 4 DOT 63 DOT 0605192142000 DOT 16587 AT access1 DOT cims DOT nyu DOT edu> <20060520020637 DOT GA5047 AT trixie DOT casa DOT cgf DOT cx> <Pine DOT GSO DOT 4 DOT 63 DOT 0605192221450 DOT 16587 AT access1 DOT cims DOT nyu DOT edu>
MIME-Version: 1.0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Fri, 19 May 2006, Igor Peshansky wrote:

> On Fri, 19 May 2006, Christopher Faylor wrote:
>
> > On Fri, May 19, 2006 at 10:01:27PM -0400, Igor Peshansky wrote:
> > >Hi,
> > >
> > >Found a weird problem with the latest CVS (a regression from end
> > >February, but I can track it down further, too, if the testcase
> > >doesn't help).  Compiling the following program:
> > >
> > >#include <stdio.h>
> > >int main() { printf("1\n"); exit(-1); }
> > >
> > >with "gcc -mno-cygwin" and running it produces the following output:
> > >
> > >1
> > >979250836 [proc_waiter] bash 5028 proc_waiter: unknown value 49 on proc pipe
> > >979250894 [proc_waiter] bash 5028 proc_waiter: unknown value 13 on proc pipe
> > >979250920 [proc_waiter] bash 5028 proc_waiter: unknown value 10 on proc pipe
> > >979264978 [proc_waiter] bash 5028 proc_waiter: unknown value 49 on proc pipe
> > >979265034 [proc_waiter] bash 5028 proc_waiter: unknown value 13 on proc pipe
> > >979267613 [proc_waiter] bash 5028 proc_waiter: unknown value 10 on proc pipe
> > >979278806 [proc_waiter] bash 5028 proc_waiter: unknown value 49 on proc pipe
> > >979278860 [proc_waiter] bash 5028 proc_waiter: unknown value 13 on proc pipe
> > >979278886 [proc_waiter] bash 5028 proc_waiter: unknown value 10 on proc pipe
> > >979289509 [proc_waiter] bash 5028 proc_waiter: unknown value 49 on proc pipe
> > >979289568 [proc_waiter] bash 5028 proc_waiter: unknown value 13 on proc pipe
> > >979289595 [proc_waiter] bash 5028 proc_waiter: unknown value 10 on proc pipe
> > >979300049 [proc_waiter] bash 5028 proc_waiter: unknown value 49 on proc pipe
> > >979300106 [proc_waiter] bash 5028 proc_waiter: unknown value 13 on proc pipe
> > >979300411 [proc_waiter] bash 5028 proc_waiter: unknown value 10 on proc pipe
> > >
> > >but (!) only in an xterm.  Try as I might, I couldn't reproduce this
> > >in rxvt or bash with CYGWIN=tty.  I don't know what the differences
> > >are, but there it is.  I did reproduce this in an xterm running tcsh
> > >and pdksh (and a perl shell, interestingly enough).  The above
> > >testcase was distilled from a huge Java program that exhibited this
> > >behavior.
> > >
> > >Note that 49 is really the character '1', and 13 and 10 are CRLF.
> > >I've also gotten other characters at times, all corresponding to
> > >valid messages from the program, printed to either stdout or stderr.
> > >The number of times it repeats also seems to vary -- in some cases
> > >it's only once, in others more (it's repeated 5 times above).
> >
> > I can't duplicate this but, I'm not really interested in this kind of
> > problem unless you can duplicate the problem with a cygwin snapshot.
> > Otherwise, there is no way of knowing how you've built the DLL or what
> > other local mods might be in it.
>
> Sorry, should've mentioned that I can also duplicate this with both the
> 20060518 and 20060516 snapshots.

Ok, with the 20060521 (and later) snapshots things became different.
This error is now more readily reproducible (on anything that uses ptys --
xterm, rxvt, bash+CYGWIN=tty), but the output has changed.  Running the
above program now results in the output repeated 5 times:

$ uname -svr
CYGWIN_NT-5.1 1.5.20s(0.155/4/2) 20060527 19:21:22
$ echo $CYGWIN
tty
$ ./B
1
1
1
1
1
1
$

I've verified that the whole output is repeated, not just the first
character or the first line.

Hopefully this will help someone track this down.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

--
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019