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

* cygwinenv.sgml: Remove CYGWIN=strace option. Update CYGWIN options.

Browse Source 
* how-programming.texinfo: Remove stuff about CYGWIN=strace.
* setup2.sgml: Remove CYGWIN=strace example.
This commit is contained in:
Christopher Faylor
2000-11-19 04:53:46 +00:00
parent 25688b70d5
commit 9f7bdd2b58
4 changed files with 14 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
winsup/doc/how-programming.texinfo
View File

@@ -397,16 +397,6 @@ programs with various debug and trace messages enabled. For information
on using @code{strace}, see the Cygwin User's Guide or the file
@code{winsup/utils/utils.sgml}.
Alternatively, you can set the @code{STRACE} environment variable to
@code{1}, and get a whole load of debug information on your screen
whenever a Cygwin app runs. This is an especially useful tool to use
when tracking bugs down inside the Cygwin library. @code{STRACE} can be
set to different values to achieve different amounts of granularity.
You can set it to @code{0x10} for information about syscalls or
@code{0x800} for signal/process handling-related info, to name two. The
strace mechanism is well documented in the Cygwin library sources in the
file @code{winsup/cygwin/include/sys/strace.h}.
@subsection Why doesn't gdb handle signals?
Unfortunately, there is only minimal signal handling support in gdb