From owner-freebsd-hackers Thu Sep 18 11:39:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA26799 for hackers-outgoing; Thu, 18 Sep 1997 11:39:56 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA26793 for ; Thu, 18 Sep 1997 11:39:54 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id LAA11157; Thu, 18 Sep 1997 11:35:26 -0700 (PDT) To: Poul-Henning Kamp cc: Graham Wheeler , gram@gram.cdsec.com.dk.tfs.com (Graham Wheeler), hackers@FreeBSD.ORG Subject: Re: Bug in malloc/free (was: Memory leak in getservbyXXX?) In-reply-to: Your message of "Thu, 18 Sep 1997 19:09:20 +0200." <10666.874602560@critter.freebsd.dk> Date: Thu, 18 Sep 1997 11:35:26 -0700 Message-ID: <11153.874607726@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Erm, never mind on that "how do I find the faulted memory location on SIGBUS" question. I just took a closer look at sigaction(2) and read about the sigcontext structure*. :-) Jordan * Though it also says that this structure is defined in when it's really in - I don't know how this has possibly escaped Bruce's eye all this time! ;-)