This is the mail archive of the
mailing list for the Cygwin project.
Re: security.cc: bug report, question and suggestion
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
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html