X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <4756E558.1A70439F@dessent.net> Date: Wed, 05 Dec 2007 09:52:24 -0800 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: 1.5.24-2: unalbe to get a core Dump file References: <47568201.80303@garr.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Massimo Carboni wrote: > # setenv CYGWIN "error_start=C:\cygwin\bin\dump.cmd"* > *** starting debugger for pid 3412, tid 3056 > 3 [main] a 3600 try_to_debug: Failed to start debugger, Win32 error 5 > *** continuing pid 3412 from debugger call (0) You can't use a .cmd file as the error_start parameter. It has to be a directly executable binary. A cmd file is not directly executable, as it has to be launched with %comspec% and that knowledge requires a higher level API like ShellExecute instead of the low level CreateProcess that is used here. As already mentioned downthread, if you want a core dump you should simply set error_start=c:/cygwin/bin/dumper.exe, modulo dumper bugs (which should have all been fixed in the latest version.) If you really must run a cmd file, then you need to create an .exe wrapper program that execs %comspec% /c "dump.cmd (original args)" or similar. Brian -- 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/