Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<A7AF87D6496DD411B50A00D0B76DEB2C1E6F3D@EX2BEBREYMBX02>
From:	Darius DOT Clynes AT cec DOT eu DOT int
To:	muller AT cerbere DOT u-strasbg DOT fr
Cc:	cygwin AT cygwin DOT com
Subject:	RE: GDB Stop button does not work. and how about a core dump?
Date:	Fri, 8 Jun 2001 19:05:52 +0200
MIME-Version:	1.0
X-Mailer:	Internet Mail Service (5.5.2650.21)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id NAA17300

>At 15:56 08/06/01 , vous avez écrit:
>>same here, stop (or break) in gdb has never worked for me either.
>>you have to set the break points before you press run,
>>then you can step further, etc. also cygwin compiled
>>exectutables does not produce a debugger readable image core dump.
>
>  Thanks for your answer, do you also use win95
>or do you have another system like NT or 2000 ?
>

i am running under NT, but I doubt that makes any difference here.

the debuggable core issue would be a great improvement.
but first cygwin would have have to dump a core. I
have no idea what that involves in detail, 
but probably it is not easy, 
(finding the starting point address
of the executable in memory and dumping everything out to a file, etc)
 


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -