Michal Hlavinka
2013-11-12 10:37:23 UTC
Hi,
I've found that iffe change between 2013-08-07 and 2013-08-14 broke some
tests. The problem is in execute() function. It added extra
argument $tmp.u
13-08-11 iffe.sh: axecuted blocks now have a sungle argument that is a
tmp file prefix
But some tests do not like it. For example vfork test in ksh. With this
change it returns
iffe: test: vfork exists and it works ... no
instead of 'yes'.
The vfork test executes itself and uses argv[1] non-existance as switch.
...
if (argv[1])
_exit(signal(SIGHUP, SIG_DFL) != SIG_IGN);
...
execv(cmd[0], cmd);
...
With the iffe change, argv[1] exists even in first execution and test
does not work correctly.
This is just one test I've found, but there may be other tests that
won't work with the iffe change.
Michal
I've found that iffe change between 2013-08-07 and 2013-08-14 broke some
tests. The problem is in execute() function. It added extra
argument $tmp.u
13-08-11 iffe.sh: axecuted blocks now have a sungle argument that is a
tmp file prefix
But some tests do not like it. For example vfork test in ksh. With this
change it returns
iffe: test: vfork exists and it works ... no
instead of 'yes'.
The vfork test executes itself and uses argv[1] non-existance as switch.
...
if (argv[1])
_exit(signal(SIGHUP, SIG_DFL) != SIG_IGN);
...
execv(cmd[0], cmd);
...
With the iffe change, argv[1] exists even in first execution and test
does not work correctly.
This is just one test I've found, but there may be other tests that
won't work with the iffe change.
Michal