From owner-freebsd-hackers Fri Oct 15 10:10:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id B94C31511F for ; Fri, 15 Oct 1999 10:10:50 -0700 (PDT) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id KAA13379; Fri, 15 Oct 1999 10:09:25 -0700 (PDT) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Fri, 15 Oct 1999 10:09:25 -0700 Date: Fri, 15 Oct 1999 10:09:24 -0700 (PDT) From: Kip Macy X-Sender: kip@luna To: Alec Kloss Cc: Dodge Ram , freebsd-hackers@freebsd.org Subject: Re: Handling segV's In-Reply-To: <199910151623.LAA25438@D2SI.COM> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: ajk@paw-in-eye.net,gupz@hotmail.com,freebsd-hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG DDD somehow manages to do this, however, even if you tell it to ignore it and continue it will almost invariably segV again shortly thereafter. -Kip On Fri, 15 Oct 1999, Alec Kloss wrote: > Dodge Ram said: > > > Hi, > > > > I am looking at ways to handle segV's gracefully without > > letting a process die. I am aware of the siglongjmp() call and don't > > know if that is the only way to handle segV's > > > > Any pointers on how to gracefully (?) handle segV and not > > letting the process die will be of great help. > > > > Also, given that I have a solution to test, what are all the > > ways I can ensure that my process handles segV's rightly ? > > > > thanks and regards, > > > > ramC > > > > Attempting to recover from a SIGSEGV seems like a very risky proposition. > Essentially, ANY writeable memory by the process may have been > clobbered before the process decided to write to read-only memory > generating the SIGSEGV. Suppose you recover and longjump somewhere > and then flush your IO buffers out to disk. For all you know, the > buffers are now total garbage, so now you have a running program > working with incorrect data on disk. > > Yikes. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message