This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: echo -n or sleep 0 needed to unblock Bourne shell script

On 27/02/2016 23:28, Matthijs Nescio wrote:

Sorry for replying in a new thread.


         I have the strangest problem. I am running some complicated advanced Bourne shell scripting. These scripts work fine under Ubuntu 14.04 LTS. However, in Cygwin I have to add some strange commands with no obvious effect; without these the scripts just hang. I can not disclose the scripts completely because they are company property. I realise that this does not comply to the rules of smart questions, but if anybody else has this problem the Cygwinners need to know about it. I do not exactly know when these problems started. I reinstalled Cygwin twice, several weeks ago and yesterday evening (25-2-2016).

         I have had this problem with several complicated, lengthy scripts. Debugging using echo debug statements is hard because the echo makes the problem go away. When I discovered similar problems in multiple scripts, I reinstalled Cygwin, but the problem persists. Also rebooting my Windows 7 Enterprise edition machine does not solve the problem. I have had some experienced colleagues to look at this and they were as flabbergasted as I was.


            TTP_FILE_DR_KML=`echo $TTP_FILE.dr.kml | sed -s 's#\.txt\.#\.#g'`
            #echo -n> /dev/null
            sleep 0
            if [ "`convert_needed "$TTP_FILE_DR_KML"`" = "convert" ]

         In the examples above and below, either the sleep or the echo has to be commented in, otherwise the script just hangs. In the example below the doit function needs the echo or sleep, otherwise it does not return.

            # 8< code removed
            #echo -n
            sleep 0

The explaination of the issue may not be clear. I have to add the sleep 0 or the echo in order to keep my scripts running. Without these the scripts hang. Sometimes they can be interrupted by CTRL-C, sometimes they do not respond. The doit() function fails to end all together without the sleep. So the sleep 0 was not there before, it is needed for the flow of the script all of a sudden.

Obviously, if adding an echo to a script changes the behaviour, it is kind of hard to prove that an empty echo has an effect. Again, I showed it to two colleagues who were surprised too. Together there was over 30 years of Bourne shell experience looking at the problem.

The script containing the doit function is single-threaded, so there is no race condition in the script. Actually, it should just end itself after the curly brace. Without either the sleep or the echo it just hangs. Note also that the reproducibility is 100%, which is not expected from a race condition of marginal time differences. With reproducibility here I mean: adding the sleep/echo gives the normal flow, removing the sleep/echo gives a hanging script.

* Were there changes in the Bourne shell interpreter in 2015/2016?

see the announcements

I suspect the list is very long.

* Are these interpreters well-tested for regression?


* Are similar issues reported?

Not that I personally remember.

Thank you, kind regards, Matthijs.

I misunderstood your first explanation.
So the script hang if you don't add one of the two commands.

>          doit()
>          {
>             8< code removed
>             #echo -n
>             #sleep 0
>          }

more than bash, the output redirection or the piping is a
likely source of hang.

For example this command serie, works differently on
cygwin than on Linux

  echo "prova" > prova.txt
  cat prova.txt
  cat prova.txt > prova.txt
  cat prova.txt

I suspect something similar is happening in your case and it is not
due to bash.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]