9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] crashing 9vx
Date: Sun, 30 May 2010 15:52:56 +0000	[thread overview]
Message-ID: <AANLkTinKJkpN7qHYecxS269NSrEhrDBVDLyKdM5Wzztn@mail.gmail.com> (raw)
In-Reply-To: <416156.63571.qm@web83915.mail.sp1.yahoo.com>

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

On Sun, May 30, 2010 at 2:46 PM, Brian L. Stuart <blstuart@bellsouth.net> wrote:
> This is weird.  I just built 9vx on FreeBSD without
> the -O3.  But instead of being more stable, that
> one crashed on startup, like Charles reported.
> Namely:
>
> 9vx panic: user fault: signo=11 addr=3850cb67 [useraddr=cb67] read=1 eip=80b973c esp=493ffac0
> 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



  reply	other threads:[~2010-05-30 15:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  4:10 ron minnich
2010-05-28  6:40 ` Philippe Anel
2010-05-28  8:13   ` Philippe Anel
2010-05-28  8:24     ` Philippe Anel
2010-05-28 15:10   ` ron minnich
2010-05-28 15:15     ` Philippe Anel
2010-05-28 15:24       ` ron minnich
2010-05-28 18:36         ` Charles Forsyth
2010-05-28 19:31           ` Philippe Anel
2010-05-28 20:46           ` ron minnich
2010-05-28 21:00             ` erik quanstrom
2010-05-29  3:39               ` ron minnich
2010-05-29  4:05                 ` EBo
2010-05-29  5:13                   ` ron minnich
2010-05-29  5:45                     ` EBo
2010-05-29  4:09                 ` erik quanstrom
2010-05-29  5:10                   ` ron minnich
2010-05-30 14:46                 ` Brian L. Stuart
2010-05-30 15:52                   ` ron minnich [this message]
2010-05-30 15:59                   ` Philippe Anel
2010-05-30 16:30                     ` erik quanstrom
2010-05-31  1:33                       ` Brian L. Stuart
2010-05-30 17:08                     ` Bakul Shah
2010-05-31  1:14                     ` Brian L. Stuart
2010-05-31  2:01                       ` ron minnich
2010-05-31 16:32                         ` ron minnich
2010-05-31 17:48                           ` jake
2010-05-31 18:16                             ` EBo
2010-05-31 20:46                           ` Jorden M
2010-06-01 11:14                             ` Charles Forsyth
2010-06-02 16:40                               ` ron minnich
2010-05-29  5:47               ` EBo
2010-10-28 14:00 yy
2010-10-28 14:47 ` Lucio De Re

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTinKJkpN7qHYecxS269NSrEhrDBVDLyKdM5Wzztn@mail.gmail.com \
    --to=rminnich@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).