From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@9fans.net
Date: Mon, 15 Dec 2008 09:55:20 +0000
From: prem <prem.mallappa@gmail.com>
Message-ID: <ee6a5c4d-4511-41f0-af73-5de403bddeb4@s9g2000prm.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
References: <88f19777-0b55-42fe-b0bd-4902d4e58eed@l33g2000pri.googlegroups.com>
Subject: Re: [9fans] 9vx on x86-64
Topicbox-Message-UUID: 61a7e82c-ead4-11e9-9d60-3106f5b1d025

> 9vx -PSX >log 2>&1
I just executed 9vx -P -S -X -r <path of dist 0.12> -u glenda

and pasted what was written on the linux console.

> 9vx -PSX 2>&1 | cat >log
this creates a log of 138 MB :( (19MB gzipped)

However, I think I solved it without actually solving it,
gcc flags changed from -g -03 to -g,
it works like a charm

/Prem

On Dec 12, 5:46�pm, r...@swtch.com (Russ Cox) wrote:
> > Aborted, here is alog with -P -S -X
> > ------------------------
> > reate new cpu: kprocq.n1 nrunproc0
> > cpu0: ready 2 *x11*; wakeup kproc cpus
>
> It seems a little odd that the log starts with
> a partial word. �It is posible that if you did
>
> 9vx -PSX >log 2>&1
>
> that somehow the fd offsets for 1 and 2 are
> not being maintained properly
> (I don't understand it, but I've seen it).
>
> Sometimes it works better to do
>
> 9vx -PSX 2>&1 | cat >log
>
> Russ