This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: (latest install from site) cygwin1.dll 1.3.22-dontuse-21 --bashbuggy behaviours under windows 2000
- From: "sandeep" <sandeep at codito dot com>
- To: "Andrew Markebo" <andrew dot markebo at comhem dot se>
- Cc: <cygwin at cygwin dot com>
- Date: Thu, 7 Aug 2003 15:22:27 +0530
- Subject: Re: (latest install from site) cygwin1.dll 1.3.22-dontuse-21 --bashbuggy behaviours under windows 2000
- References: <001c01c35cbe$cbbc9020$2564a8c0@blackmagic><m3isp9swcn.fsf@flognat.dyndns.org><003401c35cc0$8bc781d0$2564a8c0@blackmagic> <m3adalsuoe.fsf@flognat.dyndns.org>
Thanks Andrew for the tip. I have been using
set -x
....
section of script that needs debugging
...
set +x
to specifically examine how bash is treating it. This way the less but relevant
is available for examination.
----- Original Message -----
From: "Andrew Markebo" <andrew.markebo@comhem.se>
> OK hmm no idea.. meanwhile, you know that you can throw parameter "-v"
> on the shell starting the script and then you can see how the script
> expands/replaces stuff and so on.
>
> Like:
>
> bash -v scriptname
> or
> #!/bin/bash -v
>
> in the script
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.507 / Virus Database: 304 - Release Date: 8/4/2003
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/