From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <599f06db0601160540m29aa0fb1qd1416d4d4756c9cb@mail.gmail.com>
Date: Mon, 16 Jan 2006 14:40:36 +0100
From: Gorka guardiola <paurea@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: qemu --- Debug Crashing on qemu
In-Reply-To: <43CB566B.3050209@Utel.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <43CAEB4C.2000900@surferz.net>
	<5d375e920601151653m21af63cdq7bff998ec1a74ce9@mail.gmail.com>
	<43CAFBF7.3040706@surferz.net>
	<000201c61a72$e3fb9ef0$14aaa8c0@utelsystems.local>
	<43CB566B.3050209@Utel.no>
Topicbox-Message-UUID: d9d70778-ead0-11e9-9d60-3106f5b1d025

That is what I concluded :-). I was just sharing my experience...

On 1/16/06, "Nils O. Sel=E5sdal" <NOS@utel.no> wrote:
> Gorka guardiola wrote:
> > I got this error randomly on some machines. I tried with different
> > compiler versions,
> > different C libraries, different kernels, and found no pattern. The pro=
blem
> > is you dont get the code for kqemu...
> The fix should then be obvious and easy.
> Don't use kqemu.
> ever.
>


--
- curiosity sKilled the cat