* Sven Hartrumpf hartru...@gmx.net [140121 07:37]:
Hi all.
The git version of chicken shows an annoying behavior
for some time.
If I run make check, the output looks ok, but an a.out
process runs forever in the background (100% cpu usage).
It cannot be killed with SIGTERM, but only with
Hi Sven,
On Tue, 21 Jan 2014 07:36:50 +0100 (CET) Sven Hartrumpf hartru...@gmx.net
wrote:
Hi all.
The git version of chicken shows an annoying behavior
for some time.
If I run make check, the output looks ok, but an a.out
process runs forever in the background (100% cpu usage).
It cannot
* Mario Domenech Goulart mario.goul...@gmail.com [140121 10:20]:
Hi Sven,
On Tue, 21 Jan 2014 07:36:50 +0100 (CET) Sven Hartrumpf hartru...@gmx.net
wrote:
Hi all.
The git version of chicken shows an annoying behavior
for some time.
If I run make check, the output looks ok, but an
Hi Mario, hi Christian.
SH:
If I run make check, the output looks ok, but an a.out
process runs forever in the background (100% cpu usage).
It cannot be killed with SIGTERM, but only with SIGKILL.
The a.out appears at the end of make check.
MG:
Maybe it is the annoying
On Tue, Jan 21, 2014 at 10:34:22AM +0100, Christian Kellermann wrote:
Maybe it is the annoying http://bugs.call-cc.org/ticket/877
Which patch is Peter referring to in the comments?
It's the one you were taking a look at a while ago:
Hi all.
The git version of chicken shows an annoying behavior
for some time.
If I run make check, the output looks ok, but an a.out
process runs forever in the background (100% cpu usage).
It cannot be killed with SIGTERM, but only with SIGKILL.
The a.out appears at the end of make check.
(32bit
