This is the mail archive of the
mailing list for the Cygwin project.
Re: Am set up for debugging... what next.
- To: "Troy Noble" <troy dot noble at channelpoint dot com>,<cygwin at cygwin dot com>
- Subject: Re: Am set up for debugging... what next.
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Tue, 24 Apr 2001 08:13:37 +1000
- References: <8F23E55D511AD5119A6800D0B76FDDE11E0F5D@cpex3.channelpoint.com>
----- Original Message -----
From: "Troy Noble" <firstname.lastname@example.org>
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
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple