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
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 29 Jan 2002 21:58:13 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: security.cc: bug report, question and suggestion
Message-ID: <20020130025813.GF32762@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <3C4EFF65 DOT FF7BA4DE AT ieee DOT org> <3C4EFF65 DOT FF7BA4DE AT ieee DOT org> <3 DOT 0 DOT 5 DOT 32 DOT 20020129213206 DOT 007e2500 AT pop DOT ne DOT mediaone DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3.0.5.32.20020129213206.007e2500@pop.ne.mediaone.net>
User-Agent: Mutt/1.3.23.1i

On Tue, Jan 29, 2002 at 09:32:06PM -0500, Pierre A. Humblet wrote:
>--- how-to-debug-cygwin.txt.in	Tue Jan 29 20:08:10 2002
>+++ how-to-debug-cygwin.txt	Tue Jan 29 20:17:50 2002
>@@ -11,7 +11,9 @@
>
> 1. The first thing you'll need to do is to build cygwin1.dll and your crashed
> application from sources. To debug them you'll need debug information, which
>-is normally stripped from executables.
>+is normally stripped from executables. You should also define the DEBUGGING
>+macro to enable some debug features. Debug from a console window (and not
>+from windows such as rxvt), as some debugging messages go to the console.
>
> 2. Create known-working cygwin debugging environment.
> - create a separate directory, say, c:\cygdeb, and put known-working
>@@ -41,6 +43,8 @@
>   such situation: -b enables buffering of output and reduces additional
>   timeouts introduced by strace, and -m option allows you to mask certain
>   classes of *_printf() functions, reducing timeouts even more.
>+  Programs started by strace are started as if directly from Windows, and
>+  not as if from a Cygwin shell or program.
>
> 5. Problems at early startup.
>   Sometimes, something crashes at the very early stages of application

I can't comment on the security patch but I did add some similar wording
to your how-to-debug-cygwin.txt patch above.  However, your advice to
define the DEBUGGING macro isn't quite right.  You should use
"configure --enable-debugging".

Thanks.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/