From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1d5d51400807311638g4087f5c9qc2c24000acfa6fe5@mail.gmail.com>
Date: Fri,  1 Aug 2008 07:38:06 +0800
From: "Fernan Bolando" <fernanbolando@mailc.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
In-Reply-To: <20080731192213.1BDDB1E8C35@holo.morphisms.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <0e5bb5f8aed495b90516d1c2d3a37ccf@9srv.net>
	<20080731192213.1BDDB1E8C35@holo.morphisms.net>
Subject: Re: [9fans] Reliable 9vx(.OSX) crash
Topicbox-Message-UUID: f97e9cb4-ead3-11e9-9d60-3106f5b1d025

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