Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Sun, 4 Nov 2001 21:40:09 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: 20011101 snapshot broken (also 20011103) Message-ID: <20011104214009.A27568@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <2761-Fri02Nov2001224205+0000-starksb AT ebi DOT ac DOT uk> <5523-Sat03Nov2001082624+0000-starksb AT ebi DOT ac DOT uk> <6426-Mon05Nov2001011335+0000-starksb AT ebi DOT ac DOT uk> <20011104203718 DOT A3511 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i On Mon, Nov 05, 2001 at 11:32:36AM +0900, Kazuhiro Fujieda wrote: >>>> On Sun, 4 Nov 2001 20:37:18 -0500 >>>> Christopher Faylor said: > >> Oddly enough, both of the above work fine for me. >> >> If you have a clue about what is now incorrect in the handling of >> unreliable pipes, please share it. > >I'm sorry I don't have any clue at present. I tried to get >the strace log but failed by STATUS_ACCESS_VIOLATION: > >$ strace -o /tmp/sh.log sh -c '`echo tako`' > 329833 [main] SH 360109 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION > 332560 [main] SH 360109 open_stackdumpfile: Dumping stack trace to SH.EXE.stackdump >$ > >I attached /tmp/sh.log below. I also failed the JIT debugging >because gdb also died by STATUS_ACCESS_VIOLATION (NT4sp6a) or >can't attach the process (on WinME). If you are trying to attach to a process which is being straced, you can't do that because strace uses the debugging api. Otherwise, see: how-to-debug-cygwin.txt in the winsup/cygwin directory for a description of how to use a separate cygwin1.dll to debug a faulty one. cgf