From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22937 invoked by alias); 12 Dec 2004 16:36:34 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 22919 invoked from network); 12 Dec 2004 16:36:31 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 12 Dec 2004 16:36:31 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iBCGaQYj023101 for ; Sun, 12 Dec 2004 11:36:26 -0500 Received: from localhost.redhat.com (vpn50-50.rdu.redhat.com [172.16.50.50]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iBCGaQr08074; Sun, 12 Dec 2004 11:36:26 -0500 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id DA1283EF9; Sun, 12 Dec 2004 11:34:22 -0500 (EST) Message-ID: <41BC730C.6050609@gnu.org> Date: Sun, 12 Dec 2004 16:38:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Randolph Chung Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa] Add some flags to tramp frame unwinder References: <20041209172303.GF29171@tausq.org> In-Reply-To: <20041209172303.GF29171@tausq.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00330.txt.bz2 Randolph Chung wrote: > I'd like to use the generic tramp frame code for pa targets; > unfortunately hpux decided that the signal trampoline function should > have a regular function name, so we cannot use the generic > infrastructure (it considers code which is inside a function to be not a > trampoline). > > I added some flags to the tramp_frame structure to make those checks > optional. Really, I only need the "ok_inside_function" flag, but for > completeness I added "ok_inside_section" as well. Instead of this, delete the test and in its place add a comment explaining what was there. I just hit another similar case - signal trampolines on altstacks - where there's either/or a valid symbol or segment. Andrew