Mail Archives: cygwin/2006/05/19/22:07:22
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.
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/
- Raw text -