Architecture: blackfin (i think it just happens with NOMMU)

NOTE: this error does not happen with MMU compilations. But it can be forced even in pc compilation by defining the constant BUILD_AS_NOMMU to 1, at least It happens to me consistently.

if you try to execute one of the following example commands (i guess it happens with every command that have an [if|while|..] after a pipe) hush uses all the system's memory:

echo echo | while read a ; do true ; done
echo echo | while test `date +%s` -lt 9739378 ; do true; done
echo echo | while test 1 -gt 2 ; do true; done
echo a | if true; then echo a ; fi

In those cases the workaround for scripts is very simple, putting brackets in the right part:

echo echo | ( while read a ; do true ; done )
echo echo | ( while test `date +%s` -lt 9739378 ; do true; done )
echo echo | ( while test 1 -gt 2 ; do true; done )
echo a | ( if true; then echo a ; fi )

I did try to find the bug myself and just couldn't, but I know at very high level what is the error that is happening. When parsing and executing list of commands hush (at least without MMU) executes itself again with -c argument and the command fragments to be executed, for example "(echo a; echo b) | cat" execute another hush process with "echo a; echo b" command. The issue here is that with "echo a | if true; then echo a; fi" style commands it executes infinite instances of hush with that entire command ("echo a | if true; then echo a; fi" in this case) instead of a subcommand (that in this case I'm guessing is "if true; then echo a; fi" )

Sorry for not finding the bug, and just tell me if you need more information.

thanks,

Mikel Garai