README 1.3 KB

123456789101112131415161718192021222324252627282930
  1. 1) Link or copy the shell to test to "./testshell", then run the tests
  2. like this: `./test01.sh`
  3. 2) Please keep in mind that the sigint catcher program remaps SIGQUIT
  4. to C-g. When a script fails, it is possible that your terminal is left
  5. with these changes. Either you have to be careful and reset the
  6. terminal when it is needed or keep in mind that you might have to use
  7. C-g insted of C-\ for SIGQUIT.
  8. 3) Some background jobs are started and are supposed to be killed by a
  9. working shell. You wouldn't read this if you weren't concerned about
  10. the quality of your shell, so you probably have some runaway jobs when
  11. done with the tests. Make sure you `ps` for all jobs attached to your
  12. terminal when you're done. I just discovered a `wc -c /dev/zero`
  13. running on my machine since almost a week ago :-)
  14. 4) The program ./hardguy lasts 20 seconds it is not catched by the
  15. surrounding shell, no matter what happens. Patience, no need to kill
  16. it.
  17. 5) Some examples need the -T switch I just committed to
  18. FreeBSD-current's /bin/sh (immediate execution of traps).
  19. mkdep.sh tests mkdep, which is an example of a program that is
  20. implemented as shell script and need to kill itself in a trap
  21. handler. It should just be interruptable by the first SIGINT.
  22. test??[ab].sh are subshell neede for other tests, but cann be called
  23. directly as well.