X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: Alberto Luaces To: cygwin AT cygwin DOT com Subject: Re: 1.5.24-2: unalbe to get a core Dump file Date: Wed, 5 Dec 2007 12:09:36 +0100 User-Agent: KMail/1.9.7 References: <47568201 DOT 80303 AT garr DOT it> In-Reply-To: <47568201.80303@garr.it> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200712051209.37001.aluaces@udc.es> Content-Type: text/plain; charset="utf-8" X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id lB5B9LvJ020861 El Wednesday 05 December 2007 11:48:33 Massimo Carboni escribió: > Hi there, > > I'm quite new on cygwin I'm trying to get a core dump for debug purpose > without success. I think currently it is not possible to get the core file. However, you can set the debugger to attach to the process when it crashes, which is basically the same: $ export CYGWIN=error_start=c:\\cygwin\\bin\\gdb.exe (Change the path to point where your gdb.exe is). -- 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/