From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <416156.63571.qm@web83915.mail.sp1.yahoo.com>
References: <AANLkTil3is6tOfzMJg6Z03eYTZgnUBzBz9F8U4HSWw3C@mail.gmail.com>
	<416156.63571.qm@web83915.mail.sp1.yahoo.com>
Date: Sun, 30 May 2010 15:52:56 +0000
Message-ID: <AANLkTinKJkpN7qHYecxS269NSrEhrDBVDLyKdM5Wzztn@mail.gmail.com>
From: ron minnich <rminnich@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] crashing 9vx
Topicbox-Message-UUID: 2d73b642-ead6-11e9-9d60-3106f5b1d025

Here are your debug options:
        case '1':
                singlethread =3D 1;
                break;
        case 'A':
                doabort++;
                break;
        case 'B':
                abortonfault++;
                break;
        case 'K':
                tracekdev++;
                break;
        case 'F':
                nofork =3D 1;
                break;
        case 'M':
                tracemmu++;
                break;
        case 'P':
                traceprocs++;
                break;
        case 'S':
                tracesyscalls++;
                break;
        case 'U':
                nuspace =3D atoi(EARGF(usage()));
                break;
        case 'X':
                vx32_debugxlate++;
                break;

On Sun, May 30, 2010 at 2:46 PM, Brian L. Stuart <blstuart@bellsouth.net> w=
rote:
> This is weird. =A0I just built 9vx on FreeBSD without
> the -O3. =A0But instead of being more stable, that
> one crashed on startup, like Charles reported.
> Namely:
>
> 9vx panic: user fault: signo=3D11 addr=3D3850cb67 [useraddr=3Dcb67] read=
=3D1 eip=3D80b973c esp=3D493ffac0
> aborting, to dump core.

-X is super-slick. But you can probably see what can be done here.

I wonder if you could run -X with your immediate failure and put it on
pastebin.com or similar.

ron