delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2002/07/13/17:15:31

Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Sat, 13 Jul 2002 17:15:36 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Cygwin debugging enhancements
Message-ID: <20020713211536.GA9598@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
Mime-Version: 1.0
User-Agent: Mutt/1.3.23.1i

I added two things to cygwin to help with debugging the DLL itself.

The output from CYGWIN_SLEEP now includes the program name.

I sometimes set CYGWIN_SLEEP to zero just to see what is starting
and this helps figure out where crashes occur.

I also had the dll honor CYGWIN_DEBUG so that if you

set CYGWIN_DEBUG=cat

gdb.exe will be started when the cat program is detected.

I've documented this in how-to-debug-cygwin.txt.

FYI,
cgf

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019