9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] crashing 9vx
Date: Sun, 30 May 2010 10:08:32 -0700	[thread overview]
Message-ID: <20100530170833.098425B04@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sun, 30 May 2010 17:59:49 +0200." <4C028B75.8080701@bouyapop.org>

On Sun, 30 May 2010 17:59:49 +0200 Philippe Anel <xigh@bouyapop.org>  wrote:
> You also have to recompile vx library.

Doesn't help.

> Brian L. Stuart wrote:
> > With the -O3, the crashes are rare, and seem to be
> > associated with heavy I/O.

When I run s9fes (Scheme 9 from Empty Space) tests, some of
them fail or 9vx crashes and AFAIK they don't do much I/O.
They all pass on Plan9.

Just for kicks I compiled 9vx with clang-2.7.  With -O3 it
comes up fine. The initial acme window doesn't disappear
(like it does with gcc -O3) but I couldn't compile anything.
Probably I made a mistake. Will try this later.

Without -O it comes up but the initial acme window
disappears. But compiles do work now. s9fes test "GC lists"
that used to fail in random ways with gcc compiled 9vx
finishes now without complaints but "Hyper Operations"
failed, and things went downhill from there.  Rerunning
yields the same result so at least this is consistent!

So it seems there are multiple problems.



  parent reply	other threads:[~2010-05-30 17:08 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
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 [this message]
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=20100530170833.098425B04@mail.bitblocks.com \
    --to=bakul+plan9@bitblocks.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).