# HG changeset patch
# User Eli Zaretskii <eliz@gnu.org>
# Date 1179838659 0
# Node ID c0c3bc060eb34532562a8d0e2a18ae170b9a3772
# Parent  be1a4e6df859cac6500a5de232f7a8c74e68d1f3
Add information about where to find GDB, and warn against --no-debug option
to configure.bat.

diff -r be1a4e6df859 -r c0c3bc060eb3 nt/INSTALL
--- a/nt/INSTALL	Tue May 22 12:01:46 2007 +0000
+++ b/nt/INSTALL	Tue May 22 12:57:39 2007 +0000
@@ -227,6 +227,9 @@
   To configure Emacs to build with GCC or MSVC, whichever is available,
   simply change to the `nt' subdirectory and run `configure.bat' with no
   options.  To see what options are available, run `configure --help'.
+  Do NOT use the --no-debug option to configure.bat unless you are
+  absolutely sure the produced binaries will never need to be run under
+  a debugger.
 
   N.B.  It is normal to see a few error messages output while configure
   is running, when gcc support is being tested.  These cannot be
@@ -380,7 +383,8 @@
 
   You should be able to debug Emacs using the debugger that is
   appropriate for the compiler you used, namely DevStudio or Windbg if
-  compiled with MSVC, or GDB if compiled with GCC.
+  compiled with MSVC, or GDB if compiled with GCC.  (GDB for Windows
+  is available from the MinGW site, http://www.mingw.org/download.shtml.)
 
   When Emacs aborts due to a fatal internal error, Emacs on Windows
   pops up an Emacs Abort Dialog asking you whether you want to debug