From: "Russ Cox" <rsc@swtch.com>
To: fernanbolando@mailc.net, 9fans@9fans.net
Subject: Re: [9fans] Reliable 9vx(.OSX) crash
Date: Thu, 31 Jul 2008 19:50:31 -0700 [thread overview]
Message-ID: <20080801024830.173D21E8C3B@holo.morphisms.net> (raw)
In-Reply-To: <1d5d51400807311638g4087f5c9qc2c24000acfa6fe5@mail.gmail.com>
> Does this also affect 9vx.Linux version.
it affects linux, but not the 0.12 binaries.
> I have been testing a few
> ports under it and it seems to crash in different places. I have not
> been able to isolate the type of code causes it so I did not report it
> on the list. It does seem to happen when I allocate a huge amount of
> memory for a dense matrix. It will start slowing down and closes.
>
> I haven't tried getting an update from hg tip. I have been trying to
> avoid installing mercurial to get to the hg tip. Any chance we can get
> a scheduled archive of the 9vx.* just like p9p?
9vx is still experimental software.
if you are going to run it, i would
suggest installing mercurial.
there are still random things not
working right, both on linux and os x.
it is not as stable as i would like.
once it is more stable i will think
about making automatic archives,
but i'd really rather that for now,
regular users can update easily.
the 0.12 binaries don't have a pager,
so if you run them out of memory
they will probably crash. if you run
with -t you can at least see the
error messages.
russ
next prev parent reply other threads:[~2008-08-01 2:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 21:22 a
2008-07-31 19:24 ` Russ Cox
2008-07-31 23:38 ` Fernan Bolando
2008-08-01 2:50 ` Russ Cox [this message]
2008-08-05 16:28 ` Uriel
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=20080801024830.173D21E8C3B@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
--cc=fernanbolando@mailc.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).