From owner-freebsd-questions Wed Feb 13 20:45:12 2002 Delivered-To: freebsd-questions@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 741C837B400 for ; Wed, 13 Feb 2002 20:45:09 -0800 (PST) Received: from [212.238.194.207] (helo=mailhost.raggedclown.net) by post.mail.nl.demon.net with esmtp (Exim 3.33 #1) id 16bDlb-000GN2-00 for freebsd-questions@FreeBSD.org; Thu, 14 Feb 2002 04:45:07 +0000 Received: from angel.raggedclown.net (angel.raggedclown.intra [192.168.1.7]) by mailhost.raggedclown.net (Ragged Clown Mail Gateway [buffy]) with ESMTP id 92FCB13040 for ; Thu, 14 Feb 2002 05:45:06 +0100 (CET) Received: by angel.raggedclown.net (Ragged Clown Host [angel], from userid 1001) id 8467E22590; Thu, 14 Feb 2002 05:45:06 +0100 (CET) Date: Thu, 14 Feb 2002 05:45:06 +0100 From: Cliff Sarginson To: FreeBSD questions Subject: Re: bochs vga font not detected by X Message-ID: <20020214044506.GA669@raggedclown.net> References: <003501c1b056$0374d930$de56579d@india.ti.com> <008e01c1b479$361087a0$de56579d@india.ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Feb 13, 2002 at 10:00:05PM -0600, Bob Giesen wrote: > On Wednesday 13 February 2002 04:28 am, Gautham Ganapathy wrote: > > Hi > > > > mkfontdir worked. thanx a lot. however, i have a new problem. on > > running bochs, it panics and gives a message saying that SIGILL is > > not implemented. the signal manpage says that SIGILL cannot be > > trapped using signal. is there any workarond for this? bochs seems > > to work fine when, i change the config to ignore fatal errors. > > however, this could generate unpredictable errors. > > > > gautham > > Gautham, > You should be able to trap SIGILL (illegal instruction signal) > with signal(); SIGKILL (kill signal) is the one (along w/ SIGSTOP) > that signal() won't catch. > - Bob You can catch it, but it is anyone's guess what state your program will be in if you continue to run it ... -- Regards Cliff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message