From mboxrd@z Thu Jan  1 00:00:00 1970
Message-Id: <0E5D1992-C1FF-4D3E-8C8D-72D50F6971DF@kix.in>
From: Anant Narayanan <anant@kix.in>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-Reply-To: <ab4cf6420806281340y5569db9ey904d0c2c4f946d55@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v924)
Date: Sat, 28 Jun 2008 15:17:09 -0700
References: <20080628194516.5D95C1E8C35@holo.morphisms.net>
	<20080628200656.2C74D1E8C35@holo.morphisms.net>
	<ab4cf6420806281340y5569db9ey904d0c2c4f946d55@mail.gmail.com>
Subject: Re: [9fans] 9vx native OS X gui
Topicbox-Message-UUID: cb05b7aa-ead3-11e9-9d60-3106f5b1d025

Hi,

First off, 9vx is incredible! Thanks Russ and Bryan :)

> When I start 9vx, I get the following messages dumped to terminal
> repeatedly and the app hangs:
>
> cpu10: runproc spurious wakeup
> idlehands spurious wakeup

I got the new 0.11 source to build, but run into a similar error:
cpu3: runproc spurious wakeup

On 28-Jun-08, at 1:08 PM, Pietro Gagliardi wrote:
> Running the new native 9vx (which I was almost done doing myself,
> had it not been for that missing file):
>
> The process has forked and you cannot use this CoreFoundation
> functionality safely. You MUST exec().
> Break on
> __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY___YOU_MUST_EXEC__
> () to debug.

Running 9vx with the -F flag makes that error go away (tried on 10.5.3)

Regards,
Anant