Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 19 Oct 2000 12:19:52 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT sources DOT redhat DOT com
Subject: error_start=x:\somewhere\gdb.exe
Message-ID: <20001019121952.A32628@cygnus.com>
Reply-To: cygwin-developers AT sources DOT redhat DOT com
Mail-Followup-To: cygwin-developers AT sources DOT redhat DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.6i

When debugging problems in cygwin, or even in programs like make, I've
found it immensely useful to use Egor Duda's addition to Cygwin.

If you set cygwin=error_start=x:\somewhere\gdb.exe, gdb will pop up
whenever cygwin encounters a signal that will cause the program to
terminate.

For this to be effective with a buggy cygwin, y ou have to put the
gdb in a separate directory with a cygwin that has been built with
--enable-debugging so that there is no shared memory collisions.

If you compile with --enable-debugging, there are additional consistency
checks added to cygwin which will notify you when you attempt to close a
handle that shouldn't be closed.  gdb will also be started when cygwin
prints a fatal message.

FYI,
cgf