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

* how-to-debug-cygwin.txt: Fix typo.

Browse Source
This commit is contained in:
Joshua Daniel Franklin 2005-04-25 05:03:53 +00:00
parent 6fbeb6a3f0
commit 46bf13ffc0
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
winsup/cygwin/ChangeLog
View File

@ -1,3 +1,7 @@
2005-04-24 Pavel Tsekov <ptsekov@gmx.net>
* how-to-debug-cygwin.txt: Fix typo.
2005-04-22 Christopher Faylor <cgf@timesys.com> 2005-04-22 Christopher Faylor <cgf@timesys.com>
* shared.cc (user_shared_initialize): Implement locking similar to * shared.cc (user_shared_initialize): Implement locking similar to

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

@ -82,10 +82,10 @@ c:\some\path\bad_program.exe some parameters
You can also set a CYGWIN_DEBUG variable to force the debugger to pop up You can also set a CYGWIN_DEBUG variable to force the debugger to pop up
only when a certain program is run: only when a certain program is run:
set CYGWIN_DEBUG=cat.exe=gdb.exe set CYGWIN_DEBUG=cat.exe:gdb.exe
This will force gdb.exe to start when the program name contains the string This will force gdb.exe to start when the program name contains the string
"cat.exe". The '=gdb.exe' isn't really needed, since it is the default. "cat.exe". The ':gdb.exe' isn't really needed, since it is the default.
It is just there to show how you can specify a program to run when the It is just there to show how you can specify a program to run when the
program starts. You can optionally set a breakpoint on "break_here" program starts. You can optionally set a breakpoint on "break_here"
once the debugger pops up and then you can single step through the once the debugger pops up and then you can single step through the