Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
X-pair-Authenticated:	24.126.73.164
Message-ID:	<405CAFB8.5000209@kegel.com>
Date:	Sat, 20 Mar 2004 12:55:20 -0800
From:	Dan Kegel <dank AT kegel DOT com>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Minimal test case for Make crash bug
References:	<405C00BF DOT 3090507 AT kegel DOT com> <405C06C4 DOT 7030508 AT kegel DOT com> <405C6C4B DOT 90409 AT kegel DOT com> <405C939E DOT 5020909 AT kegel DOT com> <405C9695 DOT 2010609 AT kegel DOT com>
In-Reply-To:	<405C9695.2010609@kegel.com>

Dan Kegel wrote:
> Sadly, error_start didn't seem to be able to start gdb:

Thanks to Igor for pointing out that error_start must be a
DOS path.  Here's what I see once I correct that:

$ export CYGWIN=error_start:C:\\cygwin\\bin\\gdb.exe
$ make
...
(gdb) bt
#0  0x77f75a59 in ntdll!DbgUiConnectToDbg ()
    from /cygdrive/c/WINDOWS/System32/ntdll.dll
#1  0x77f5f31f in ntdll!KiUserCallbackDispatcher ()
    from /cygdrive/c/WINDOWS/System32/ntdll.dll
#2  0x00000005 in ?? ()
#3  0x00000004 in ?? ()
#4  0x00000001 in ?? ()
#5  0x006effd0 in ?? ()
#6  0x82ba40e8 in ?? ()
#7  0xffffffff in ?? ()
#8  0x77fa88f0 in wcstombs () from /cygdrive/c/WINDOWS/System32/ntdll.dll

Unfortunately, that's also about what I see when I do
$ export CYGWIN=error_start:C:\\cygwin\\bin\\gdb.exe
$ ./a.exe

where a.exe is the following compiled with cygwin's gcc:
#include <stdio.h>
int main(int argc, char **argv)
{
         int *x;
         x = 0;
         printf("Null is %d\n", *x);
}

Looking at the other two threads (why are there three?)
doesn't help.

The stackdump file seems more informative than the gdb
started with error_start.  Has anyone used gdb from
this context with success lately?  gdb has no problem
with a.exe when run normally.
- Dan


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

- Raw text -