From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 487 invoked by alias); 12 Jul 2007 15:10:02 -0000 Received: (qmail 442 invoked by uid 22791); 12 Jul 2007 15:10:00 -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; Thu, 12 Jul 2007 15:09:56 +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 l6CF9sOg028263 for ; Thu, 12 Jul 2007 11:09:54 -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 l6CF9rEp028268; Thu, 12 Jul 2007 11:09:53 -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 l6CF9pNI006007; Thu, 12 Jul 2007 11:09:52 -0400 Message-ID: <46964453.1010608@redhat.com> Date: Thu, 12 Jul 2007 15:10: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: <20070710184623.A1F904D0585@magilla.localdomain> In-Reply-To: <20070710184623.A1F904D0585@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/msg00098.txt.bz2 Roland McGrath wrote: >> Unless I'm mistaken, it isn't possible to attach the abort signal as it >> may be sent to any thread? >> > > Good, I'll add code to attempt that. > You are mistaken. If you are catching the signal, you will catch all such > signals in whatever thread they are delivered. Anyway, abort is equivalent > to raise (SIGABRT), which means synchronously to the calling thread (the > signal will appear to happen immediately after the syscall instruction for > the syscall that performs the "raise"). > > >> 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. >> > > Like I said, when one of these hits, you are lucky if all memory is not > randomly clobbered already. But if you just avoid anything that would call > into elfutils libs at all, you might be avoiding the memory that is > definitely clobbered already, and be lucky enough to survive long enough to > withdraw gracefully. > > > Thanks, > Roland >