9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fernan Bolando" <fernanbolando@mailc.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Reliable 9vx(.OSX) crash
Date: Fri,  1 Aug 2008 07:38:06 +0800	[thread overview]
Message-ID: <1d5d51400807311638g4087f5c9qc2c24000acfa6fe5@mail.gmail.com> (raw)
In-Reply-To: <20080731192213.1BDDB1E8C35@holo.morphisms.net>

Does this also affect 9vx.Linux version. 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?


On 8/1/08, Russ Cox <rsc@swtch.com> wrote:
>> Within 9vx, something is printed which looks like the same
>> message from the drawterm'd crash, but goes away before I
>> can be sure.
>
> This is just an acme font bug that causes acme to suicide.
>
> In the latest 9vx I had left turned on the flag
> that causes core dumps when 9vx panics,
> but I forgot that that flag also causes 9vx to
> abort when any program suicides (useful when
> you suspect 9vx is the problem, not the program).
> I changed the flag not to do that.
>
> So now acme suicides but 9vx continues.
>
> Russ
>
>
>


--
http://www.fernski.com



  reply	other threads:[~2008-07-31 23:38 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 [this message]
2008-08-01  2:50     ` Russ Cox
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=1d5d51400807311638g4087f5c9qc2c24000acfa6fe5@mail.gmail.com \
    --to=fernanbolando@mailc.net \
    --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).