From: Clint Adams <schizo@debian.org>
To: "Christian T. Steigies" <cts@debian.org>
Cc: zsh-workers@sunsite.dk, troup@debian.org,
sbuild@packages.debian.org, Q@ping.be
Subject: Re: zsh (4.2.0-10)
Date: Thu, 13 May 2004 12:06:04 -0400 [thread overview]
Message-ID: <20040513160604.GA1922@scowler.net> (raw)
In-Reply-To: <20040513144300.GA26771@auric.debian.org>
> 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.
next prev parent reply other threads:[~2004-05-13 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040513074011.GA31678@skeeve>
[not found] ` <20040513132408.GA32597@scowler.net>
[not found] ` <20040513133541.GA24070@auric.debian.org>
[not found] ` <20040513140213.GA26274@auric.debian.org>
2004-05-13 14:12 ` Clint Adams
[not found] ` <20040513144300.GA26771@auric.debian.org>
2004-05-13 16:06 ` Clint Adams [this message]
2004-05-13 21:30 ` Clint Adams
[not found] ` <20040513192544.GA11594@skeeve>
2004-05-14 2:56 ` Goswin von Brederlow
2004-05-14 4:29 ` Clint Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040513160604.GA1922@scowler.net \
--to=schizo@debian.org \
--cc=Q@ping.be \
--cc=cts@debian.org \
--cc=sbuild@packages.debian.org \
--cc=troup@debian.org \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).