From owner-freebsd-hackers Tue Jun 8 14:44:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 254B714BE3 for ; Tue, 8 Jun 1999 14:44:32 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA09187; Tue, 8 Jun 1999 17:44:58 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA19231; Tue, 8 Jun 1999 17:44:19 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.2/8.6.9) id RAA09700; Tue, 8 Jun 1999 17:44:19 -0400 (EDT) Date: Tue, 8 Jun 1999 17:44:19 -0400 (EDT) From: Thomas David Rivers Message-Id: <199906082144.RAA09700@lakes.dignus.com> To: dan@trinsec.com, hackers@FreeBSD.ORG Subject: Re: Segfault in longjmp() ? In-Reply-To: <19990608174906.E69896@trinsec.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The machine is a SMP 3.0-RELEASE box. > > A heavily threaded program is segfaulting in the longjmp() function. > Any ideas what would cause this? > > Regards, > > Dan > > You could have trashed your jmp_buf... (i.e. you're passing bad data to longjmp().) Just a thought... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message