X-Spam-Check-By: sourceware.org Date: Fri, 30 Dec 2005 23:50:28 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.18-1: Crash launching COMMAND.COM (W98) Message-ID: <20051231045028.GA28454@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <1125870155 DOT 32392 DOT ezmlm AT cygwin DOT com> <431BFA1D DOT 5040903 AT cs DOT yale DOT edu> <20050905174859 DOT GB3621 AT trixie DOT casa DOT cgf DOT cx> <431CA835 DOT 5060502 AT cs DOT yale DOT edu> <431CA98A DOT 5070806 AT byu DOT net> <431CACC0 DOT 3060009 AT cs DOT yale DOT edu> <43b35194 AT wupperonline DOT de> <20051231043720 DOT GC2322 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051231043720.GC2322@trixie.casa.cgf.cx> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Fri, Dec 30, 2005 at 11:37:20PM -0500, Christopher Faylor wrote: >On Thu, Dec 29, 2005 at 04:07:00AM +0100, Ingo Brueckl wrote: >>On Mon, 05 Sep 2005, Sean Gugler wrote: >> >>> Score! Snapshot 20050905 did the trick. >> >>Unfortunately, there is still a crash with: >> >> #include >> #include >> #include >> #include >> >> int cygwinsystem (const char *cmd) >> { >> pid_t pid; >> int rc; >> static int result; >> >> if (!(pid = fork())) >> { >> char *com = getenv("COMSPEC"); >> if (!com) com = "COMMAND.COM"; >> >> if (cmd) rc = execlp(com, com, "/c", cmd, NULL); >> else rc = execlp(com, com, NULL); >> >> exit(rc); >> } >> wait(&result); >> return result; >> } >> >> int main (int argc, char **argv) >> { >> return cygwinsystem(argv[1]); >> } >> >>When calling this program with an argument like 'dir'. The dir listing >>appears, but then the program crashes. Tested with latest snapshot 20051227. > >No crash here. > >cygcheck output would help. ...as would some indication of what you mean by "crash", i.e., maybe even running this under gdb to find out precisely where the "crash" is happening. 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/