JehanneOS/newlib
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

fix typos

Browse Source
This commit is contained in:
Egor Duda 2001-10-09 18:12:51 +00:00
parent e898b6c0c7
commit 132a3b30b9
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
winsup/cygwin/how-to-debug-cygwin.txt
View File

@ -1,12 +1,12 @@
Copyright 2001 Red Hat Inc., Egor Duda
So, your favourite program has crashed? And did you say something about
So, your favorite program has crashed? And did you say something about
'stackdump'? Or it just prints its output from left to right and upside-down?
Well, you can file an angry bug report and wait until some of the core
developers try to reproduce your problem, try to find what's the matter
with your program and cygwin and fix the bug, if any. But you can do something
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
fix it, your analysis may be very helpful. Here's the (incomplete) howto on
cygwin debugging.
1. The first thing you'll need to do is to build cygwin1.dll and your crashed
@ -19,7 +19,7 @@ is normally stripped from executables.
- create a wrapper c:\cygdeb\debug_wrapper.cmd:
========= debug_wrapper.cmd =========
rem setting CYGWIN_TESTING environement variable makes cygwin application
rem setting CYGWIN_TESTING environment variable makes cygwin application
rem not to interfere with other already running cygwin applications.
set CYGWIN_TESTING=1
c:\cygdeb\gdb.exe -nw %1 %2
@ -36,7 +36,7 @@ c:\cygdeb\gdb.exe -nw %1 %2
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
may mysteriously disappear once the program is run under strace. Then the
bug is likely a race condition. strace has two useful options to deal with
such situation: -b enables buffering of output and reduces additional
timeouts introduced by strace, and -m option allows you to mask certain
@ -48,7 +48,7 @@ c:\cygdeb\gdb.exe -nw %1 %2
another environment variable that may help. Create program_wrapper.cmd:
========= program_wrapper.cmd =========
rem setting CYGWIN_SLEEP environement variable makes cygwin application
rem setting CYGWIN_SLEEP environment variable makes cygwin application
rem to sleep for x milliseconds at startup
set CYGWIN_SLEEP=20000
c:\some\path\bad_program.exe some parameters
@ -70,4 +70,4 @@ c:\some\path\bad_program.exe some parameters
build special version of cygwin1.dll which includes heap sanity checking.
To do it, just add --enable-malloc-debugging option to configure. Be warned,
however, that this version of dll is _very_ slow (10-100 times slower than
normal), so use it only when absolutely neccessary.
normal), so use it only when absolutely necessary.