From owner-freebsd-current Thu Sep 30 12:42:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id 4C551152F6 for ; Thu, 30 Sep 1999 12:42:32 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id NAA07576; Thu, 30 Sep 1999 13:42:23 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id NAA29570; Thu, 30 Sep 1999 13:42:22 -0600 Date: Thu, 30 Sep 1999 13:42:22 -0600 Message-Id: <199909301942.NAA29570@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Polstra Cc: marcel@scc.nl, current@FreeBSD.ORG Subject: Re: Now that sigcontext is gone ... In-Reply-To: References: X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm trying to digest the recent signal changes and get a handle on > what I need to do to make Modula-3 work. There is code in the runtime > currently which catches SIGBUS and uses the sigcontext's "sc_err" > member to find out the faulting address. That should be replaced > by the siginfo_t's "si_addr" member. But as far as I can tell from > grepping the kernel sources, that functionality isn't implemented. > > Is that right? Any ideas regarding a work-around? I'm also very interested in this, so if you could post this information publically, it would be greatly appreciated.... Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message