X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
Subject:	GDB
Date:	Mon, 16 Oct 2006 13:14:27 +0200
Message-ID:	<5A51C4463467BE4085066AB583A3863E024DC45A@srv-exch1.DOM-METROHM>
From:	"Schraner, Philipp" <schr AT metrohm DOT ch>
To:	<cygwin AT cygwin DOT com>
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id k9GBEfI1023479

Gnu debugger (6.3 and 6.5) for cygwin (called cygwin-special in version-postfix) seems to have a burried feature. How can it manage that Eclipse stops a running process? A standard compiled gdb is not able to do so. cygwin-special gdb uses some DLLs not implicitly clear to know why (i.e. COMCTRL.DLL, Tickle DLLs). Are they used therefore? Is it a redhat secret how it works (non-open-source)?
If possible, please let me know how to manage that the signal(..) function can be used for CTRL+C on standard streams owned by a windows application as Eclipse.
With best regards
Philipp Schraner

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