X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 21 May 2012 18:42:37 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: bash.exe.stackdump generated using cygwin 1.7.15
Message-ID: <20120521164237.GQ7763@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <OFACB7A0E1 DOT 4C1281AB-ONC1257A05 DOT 0054A369-C1257A05 DOT 0054DC8F AT it DOT ibm DOT com> <20120521155853 DOT GN7763 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20120521155853.GN7763@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
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 May 21 17:58, Corinna Vinschen wrote:
> On May 21 17:26, Alessandro Raniolo wrote:
> > 'm experiencing this issue when I run this simple testcase:
> > 
> > just run the command 
> > 
> > c:\cygwin\bin\bash.exe --login -c "/bin/mkpasswd -l > /etc/passwd"
> > 
> > it produces: 
> > [...]
> >   261 [main] bash 6636 exception::handle: Exception: STATUS_ACCESS_VIOLATION
> >  1237 [main] bash 6636 open_stackdumpfile: Dumping stack trace to bash.exe.stackdump
> 
> I can easily reproduce it even calling just /bin/echo and even under
> strace using a command like this from CMD:
> 
>   C:\cygwin\bin\strace -o bash.trace -o bash.trace \
>     c:\cygwin\bin\bash -c "/bin/echo hello > /etc/foo"
> 
> It's weird.  On my machine it only occurs when redirecting echo's stdout
> to a file, and *only* if redirected to some arbitrary file under /etc.
> For instance, echo > /usr/foo works fine, only /etc/foo crashes.
> 
> The crash occurs after echo exited, so bash wakes up from the wait4
> call.  However, the problem is that the crash does not occur in Cygwin,
> but in bash itself.
> 
>   147  350775 [main] bash 3548 wait4: 2320 = wait4(-1, 0x0, 0, 0x0)
>   --- Process 3548, exception C0000005 at 00422B0A
> 
> Eric, can you reproduce this and see where it happens?  I'm pretty sure
> it's a bug in Cygwin, not in bash, but it would be interesting to learn
> what bash did at the time the crash happened.

Incidentally I built bash without -O2 option for better debugging and
the problem vanished.  Then I built bash again with default optimization
and the crash still didn't occur.  I built from the latest bash src
package.4.1.10-4 using cygport.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple