X-Spam-Check-By: sourceware.org
Message-ID: <45B8EC37.9695C8A4@dessent.net>
Date: Thu, 25 Jan 2007 09:43:19 -0800
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: gdb coredumps on any executable
References: <Pine DOT GSO DOT 4 DOT 63 DOT 0701221444550 DOT 26586 AT access1 DOT cims DOT nyu DOT edu> <Pine DOT GSO DOT 4 DOT 63 DOT 0701251231500 DOT 28204 AT access1 DOT cims DOT nyu DOT edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

Igor Peshansky wrote:

> Ping.  Did this get overlooked?  Can people at least confirm that this
> works for them on the same setup, so I can start looking for a problem in
> my local installation?

Yes, it does work fine here.  I don't know if there's anything
noteworthy about my setup, although I am using a self-built Cygwin DLL
from fresh vintage, but I'm quite sure that I never saw this when using
a stock release either.  I tried from both a pty and a windows console,
that didn't make a difference.

One suggestion if you want to try debugging this is that if you build
gdb from source and run it from its build dir (where it creates a
.gdbinit) it has special support for debugging itself, i.e. gdb inside
gdb.  That of course assumes that the version you build doesn't also
fault.

Another suggestion that can work would be to set error_start to a native
debugger such as windbg.exe or (my favorite) OllyDbg.  The error_start
method puts the PID on the command line and I think both of those
debuggers can accept a PID as parameter, but you might have to also
supply an argument/flag.  I forget the details here but I seem to recall
that I got it working at one point.  At any rate, you'll at least get a
picture of the stack and a disassembly of the faulting location, but
none of the debugging symbols will be of any use as the native debuggers
all grok PDB and not stabs.

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/