Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com From: "Ronald Landheer" To: "Ronald Landheer" , Subject: RE: Possible bug: SH failure when calling command.com Date: Wed, 19 Sep 2001 21:09:18 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id PAA32692 Hello all, Because I was swamped in responses from this list (i.e.: I got one) I though it might be necesarry to debug ash, because this is apparently a hot topic (not). I have not found any bugs in the ash source code - in fact, when I run from gdb, the error does not occur, which is kinda strange. The last call before command.com is executed is execve (cmd="/cygdrive/c/windows.000/command.com"), which, IIRC, is handled by the Cygwin DLL. This is starting to itch - anyone wanna help scratch? (can't quite reach it). Greetz! Ronald -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/