From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <AANLkTin8_MZ0B8GSDDSa-k87aOi2-88zpN4n2suHv5gd@mail.gmail.com>
References: <AANLkTin8_MZ0B8GSDDSa-k87aOi2-88zpN4n2suHv5gd@mail.gmail.com>
Date: Tue, 11 Jan 2011 19:03:18 +0200
Message-ID: <AANLkTi=6nmqYK8VHphhO2im-_QNwB836KguQP3oZaaMN@mail.gmail.com>
From: Pavel Zholkover <paulzhol@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [9fans] plan9 go output faults on 9vx but ok on cpu
Topicbox-Message-UUID: 94add54a-ead6-11e9-9d60-3106f5b1d025

I'm typing from my phone so I don't have go sources in front of me,
but 0xdfffefc0 looks like the address I used for per thread G and M
structs - just bellow struct Tos.

Andrey and I also tried running on a 32-bit 9vx with the same effect.

Is 9vx using a different memory layout than Plan 9?

On Tuesday, January 11, 2011, Skip Tavakkolian
<skip.tavakkolian@gmail.com> wrote:
> hell-o.go is like hello.go but uses println. 8.hell-o works properly
> on a plan9 cpu. but it faults when running on 9vx. i built vx32 --
> including 9vx -- on a linux/x86-64 from sources in the last couple of
> days.
>
> % 8.hell-o
> 8.hell-o 270: suicide: sys: trap: page fault pc=3D0x000010bc
>
> /dev/kprint reports:
> 270 8.hell-o: unhandled fault va=3Dffffffffdfffefc0 [218f7fc0] eip=3D10bc
> cpu0: registers for 8.hell-o 270
> FLAGS=3D0 TRAP=3D0 ECODE=3D0 PC=3D10BC USP=3DFFFFF00
>  =A0AX 00018D60 =A0BX 0FFFFF8C =A0CX 00018DF8 =A0DX 0001C608
>  =A0SI 0FFFFFA8 =A0DI FFFFFFF8 =A0BP 00000000
>
> -Skip
>
>