diff --git a/winsup/cygwin/ChangeLog b/winsup/cygwin/ChangeLog index 6cf5997e2..d23e35e33 100644 --- a/winsup/cygwin/ChangeLog +++ b/winsup/cygwin/ChangeLog @@ -1,3 +1,7 @@ +2005-04-24 Pavel Tsekov + + * how-to-debug-cygwin.txt: Fix typo. + 2005-04-22 Christopher Faylor * shared.cc (user_shared_initialize): Implement locking similar to diff --git a/winsup/cygwin/how-to-debug-cygwin.txt b/winsup/cygwin/how-to-debug-cygwin.txt index cf10bafe7..bf7c7a6fb 100644 --- a/winsup/cygwin/how-to-debug-cygwin.txt +++ b/winsup/cygwin/how-to-debug-cygwin.txt @@ -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 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 - "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 program starts. You can optionally set a breakpoint on "break_here" once the debugger pops up and then you can single step through the