Am set up for debugging... what next.

Robert Collins robert.collins@itdomain.com.au
Mon Apr 23 15:13:00 GMT 2001


----- Original Message -----
From: "Troy Noble" <troy.noble@channelpoint.com>
To: <cygwin@cygwin.com>
Sent: Tuesday, April 24, 2001 7:56 AM
Subject: Am set up for debugging... what next.


> - created a /gdb-working/startup_gdb.cmd that reads:
>
>      set CYGWIN_TESTING=1
>      set PATH=c:\gdb-working;%PATH%
>      c:\gdb-working\gdb.exe %1 %2
>
> - in my .basrhc I set:
>
>      export CYGWIN='error_start=c:\gdb-working\start_gdb.cmd'
>
>      and started a new bash window of course, echo $CYGWIN
>      looks right.
>

Here's your problem: CYGWIN environment variable changes only affect
CYGWIN if they are set _before_ cygwinstarts.

If you're on NT, set cygwin via the system control panel or the .bat or
.cmd file that runs cygwin. If you run any cygwin daemons/services use
the system control panel. For 16 bit ^H^H^H^H^H^Hwin9x platforms set it
via autoexec.bat

Rob


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple



More information about the Cygwin mailing list