From 1d1c6baa7b6d235dec1d8b2a562561e80af4c620 Mon Sep 17 00:00:00 2001 From: Christopher Faylor Date: Sun, 16 Sep 2001 02:56:48 +0000 Subject: [PATCH] minor typo fixes. --- winsup/cygwin/how-to-debug-cygwin.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/winsup/cygwin/how-to-debug-cygwin.txt b/winsup/cygwin/how-to-debug-cygwin.txt index e5c1425e6..731cc1d71 100644 --- a/winsup/cygwin/how-to-debug-cygwin.txt +++ b/winsup/cygwin/how-to-debug-cygwin.txt @@ -9,13 +9,13 @@ better than that. You can debug the problem yourself, and even if you can't fix it, your analysis may be very helpful. Here's the (incoplete) howto on cygwin debugging. -1. The first thing you'll need to do is to build cygwin1.dll and crashed your +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. 2. Create known-working cygwin debugging environment. - create a separate directory, say, c:\cygdeb, and put known-working - cygwin1.dll, gdb.exe in it. + cygwin1.dll and gdb.exe in it. - create a wrapper c:\cygdeb\debug_wrapper.cmd: ========= debug_wrapper.cmd ========= @@ -33,7 +33,7 @@ c:\cygdeb\gdb.exe -nw %1 %2 4. Strace. You can run your program under 'strace' utility, described if user's manual. - If you know, where the problem approximately is, you can add a bunch of + If you know where the problem approximately is, you can add a bunch of additional debug_printf()s in the source code and see what they print in strace log. There's one common problem with this method, that some bugs may misteriously disappear once the program is run under strace. Then the