Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Fri, 29 Aug 2003 11:43:01 +0100
From: Elfyn McBratney <elfyn AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: RE : tee core dumped
Message-ID: <20030829104301.GK614@emcb.co.uk>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <000701c36c8a$92620590$0500a8c0 AT jle DOT ch> <002301c36e15$f27f3f60$0500a8c0 AT jle DOT ch>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <002301c36e15$f27f3f60$0500a8c0@jle.ch>
User-Agent: Mutt/1.4.1i

Philippe Torche wrote:
> No body arrived to reproduce this ?
> Actually I can produce this sometimes using isql from MS, gawk, ...
> It's for me a very big problem !
> 
> Please help me !

Calm down!  The last two weeks have been stressful for most with all of
the viruses and spam flying around on the list.  It's easy to miss *1*
post.

> [...]
> I found a problem with tee (probably), please try this sample code
> below. I've found the same problem with other tools like gawk, ...
> 
> echo '#!/usr/bin/bash
> sleep 10 > /dev/null 2>&1 &
> transfert_job=$!
> 
> echo LINENO=$LINENO
> procps -p $transfert_job -o 'pid,ppid'
> echo LINENO=$LINENO
> ' > test.sh
> chmod +x test.sh
> # OK
> test.sh > test.out
> # KO KO KO KO KO KO KO KO KO KO KO KO KO KO
> test.sh | tee test.out
> # Segmentation fault (core dumped)

I can re-produce this (same as above) and from within gdb, with a SEGV as a
result of both.  I don't have a debug version installed, so if anyone else
does and want's to try and help out.  :-)

> [...]
> ========================================
> $ cat tee.exe.stackdump
> Exception: STATUS_ACCESS_VIOLATION at eip=610BA041
> eax=00000000 ebx=615F1F50 ecx=FFFFFFFF edx=6F6C5C72 esi=0076FE9C
> edi=6F6C5C72 ebp=0076FE74 esp=0076FE70 program=C:\cygwin\bin\tee.exe
> cs=001B ds=0023 es=0023 fs=0038 gs=0000 ss=0023 Stack trace:
> Frame     Function  Args
> 0076FE74  610BA041  (6F6C5C72, 0076FEA0, 00000004, 0076FE9C) 0076FEB4
> 6105828B  (00A20000, 00000000, 00000000, FFFFFFFF) 0076FF04  61077738
> (FFFFFFFE, 00000010, 00000000, 00000000) 0076FF84  61077CC8  (610D1B58,
> 00000000, 858A88E0, 804FAB78) 0076FFB4  610053C8  (610D1B58, 00000000,
> 0022FC44, 610D1B58)
>       3 [sig] tee 2400 handle_exceptions: Error while dumping state
> (probably corrupted stack)
> [...]

Please do not inline cygcheck output, always attach it *to the mail*.  It
create's false positives for those searching the archives, and can be a real
pain if your looking for something and all you get is masses and masses of
hits from people's mail that has inlined cygcheck output.

-- Elfyn

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