Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dave DOT korn AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: how to get a coredump [was RE: Asterisk Cygwin]
Date: Thu, 27 Oct 2005 17:40:47 +0100
MIME-Version: 1.0
Content-Type: text/plain; 	charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.LNX.4.62.0510271213100.3871@ns.pyerotechnics.com>
Message-ID: <SERRANOmZp0mmhQZiCT000002b4@SERRANO.CAM.ARTIMI.COM>

Jason Pyeron wrote:
> As I don't use debuggers every day, I am posing this to the list:
> 
> 
> On Mon, 24 Oct 2005, Jerris, Michael MI wrote:
> 
>> With the patch on that bug in mantis, everything compiles great and
>> starts, but I am getting segfaults when I try to pass calls.  Do you
>> know how to get a coredump, I don't seem to be able to on my machine,
>> just a stackdump which is basically useless.

  You can't.  Cygwin doesn't do core.

  Having said that, as long as you've built the executable with debugging info
('-g'), the stackdump isn't completely useless at all.  Cut'n'paste the
addresses in the second column of the file into "addr2line
--exe=<path/to/executable>" - this is easily done by cat'ing the file in a
bash shell in a standard DOS box and using the rectangular cut'n'paste feature
it provides.  That should show you a backtrace with source file/line numbers,
at any rate.

  Other than that, why not just run the exe under gdb, so that it will catch
the segfault when and where it happens?


    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/