Re: zsh (4.2.0-10)

[Clint Adams <schizo@xxxxxxxxxx>]

> Oups... I tried it locally, ran top in one shell, SIGSTOP (and also STOP)
> stop the process like ctrl-z. With SIGCONT or CONT it somehow starts again,
> but not for very long. Is this really supposed to work?

As I recall, if you kill the right process with a SIGTERM or something,
then send SIGCONT to the remaining processes, it will proceed to the
other tests and complete the build successfully.

> Yes. I was wondering, too. The previous build worked out fine, it was built
> on a different box. I also had zsh-beta a couple of times and zsh_4.2.0-7 on
> my mac without problems, so maybe its something fancy with the Amiga? I got
> an ICE while building gcc-snapshot on the Amiga where a mac crashed only
> much later. Should I try to build it on another box? Currently we have some
> CPU cycles to kill on m68k, I'll just try t build it on my mac.

I find it curious that only sbuild exposes this problem, and now that
it's manifesting on multiple architectures, I have even less of an idea
of what the problem could be.

I wonder if a simple perl script which merely did the same signal handling as
sbuild and ran zsh's make check would give the same result.