From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2715 invoked from network); 13 May 2004 16:07:04 -0000 Received: from thor.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.86) by ns1.primenet.com.au with SMTP; 13 May 2004 16:07:04 -0000 Received: (qmail 6050 invoked from network); 13 May 2004 16:06:44 -0000 Received: from sunsite.dk (130.225.247.90) by a.mx.sunsite.dk with SMTP; 13 May 2004 16:06:44 -0000 Received: (qmail 14931 invoked by alias); 13 May 2004 16:06:42 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 19937 Received: (qmail 14921 invoked from network); 13 May 2004 16:06:41 -0000 Received: from thor.dotsrc.org (HELO a.mx.sunsite.dk) (qmailr@130.225.247.86) by sunsite.dk with SMTP; 13 May 2004 16:06:38 -0000 Received: (qmail 5845 invoked from network); 13 May 2004 16:06:38 -0000 Received: from acolyte.scowler.net (216.254.112.45) by a.mx.sunsite.dk with SMTP; 13 May 2004 16:06:36 -0000 Received: by acolyte.scowler.net (Postfix, from userid 1000) id EA2387004A; Thu, 13 May 2004 12:06:04 -0400 (EDT) Date: Thu, 13 May 2004 12:06:04 -0400 From: Clint Adams To: "Christian T. Steigies" Cc: zsh-workers@sunsite.dk, troup@debian.org, sbuild@packages.debian.org, Q@ping.be Subject: Re: zsh (4.2.0-10) Message-ID: <20040513160604.GA1922@scowler.net> References: <20040513074011.GA31678@skeeve> <20040513132408.GA32597@scowler.net> <20040513133541.GA24070@auric.debian.org> <20040513140213.GA26274@auric.debian.org> <20040513141237.GA525@scowler.net> <20040513144300.GA26771@auric.debian.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040513144300.GA26771@auric.debian.org> User-Agent: Mutt/1.5.5.1+cvs20040105i X-Spam-Checker-Version: SpamAssassin 2.63 on a.mx.sunsite.dk X-Spam-Level: X-Spam-Status: No, hits=0.0 required=6.0 tests=none autolearn=no version=2.63 X-Spam-Hits: 0.0 > 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.