From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12025 invoked by alias); 10 Jul 2007 15:34:06 -0000 Received: (qmail 12014 invoked by uid 22791); 10 Jul 2007 15:34:05 -0000 X-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,DK_POLICY_SIGNSOME,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 10 Jul 2007 15:34:02 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.13.1/8.13.1) with ESMTP id l6AFXx5O006751 for ; Tue, 10 Jul 2007 11:33:59 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [10.11.255.20]) by int-mx1.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l6AFXwl6013102; Tue, 10 Jul 2007 11:33:58 -0400 Received: from [127.0.0.1] (sebastian-int.corp.redhat.com [172.16.52.221]) by pobox.corp.redhat.com (8.13.1/8.13.1) with ESMTP id l6AFXvqH009515; Tue, 10 Jul 2007 11:33:57 -0400 Message-ID: <4693A6F6.8030403@redhat.com> Date: Tue, 10 Jul 2007 15:34:00 -0000 From: Andrew Cagney User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: Roland McGrath CC: frysk@sourceware.org Subject: Re: elfutls using assert References: <20070709230811.DCB0C4D0585@magilla.localdomain> In-Reply-To: <20070709230811.DCB0C4D0585@magilla.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact frysk-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: frysk-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00067.txt.bz2 Unless I'm mistaken, it isn't possible to attach the abort signal as it may be sent to any thread? Anyway, to make the problem more concrete, when a panic like this occurs, frysk needs time to pull all inserted breakpoints before detaching from the program and exiting. Andrew Roland McGrath wrote: > No, there is no way not to call abort. It is used for situations that are > pathological in the same way as a clobbered pointer that might lead to a > crash. If you want to improve recovery from such bugs, you might as well > catch all unexpected fatal signals and diagnose gracefully there (maybe if > things aren't too bad you can throw an exception from the signal handler > and never consult the clobbered data structures while reporting and exiting). >