From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8689 invoked by alias); 1 Nov 2004 16:15:53 -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 8680 invoked from network); 1 Nov 2004 16:15:52 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sourceware.org with SMTP; 1 Nov 2004 16:15:52 -0000 Received: from drow by nevyn.them.org with local (Exim 4.34 #1 (Debian)) id 1COeqW-00071y-9j; Mon, 01 Nov 2004 11:15:52 -0500 Date: Mon, 01 Nov 2004 16:15:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: gdb-patches@sources.redhat.com, ezannoni@redhat.com, cagney@gnu.org, roland@redhat.com Subject: Re: [rfa] Attach vsyscall support for GNU/Linux Message-ID: <20041101161552.GA26993@nevyn.them.org> Mail-Followup-To: Mark Kettenis , gdb-patches@sources.redhat.com, ezannoni@redhat.com, cagney@gnu.org, roland@redhat.com References: <20041024185345.GB22700@nevyn.them.org> <200410242054.i9OKsjnl028328@elgar.sibelius.xs4all.nl> <20041024231636.GA21927@nevyn.them.org> <200410252212.i9PMCQhJ031724@elgar.sibelius.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410252212.i9PMCQhJ031724@elgar.sibelius.xs4all.nl> User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-11/txt/msg00016.txt.bz2 On Tue, Oct 26, 2004 at 12:12:26AM +0200, Mark Kettenis wrote: > Date: Sun, 24 Oct 2004 19:16:36 -0400 > From: Daniel Jacobowitz > > Thanks for the explanation Daniel! > > Unwinding bugs aside, I think it's valuable for GDB to know that it is > at a signal trampoline. I think the custom display in backtrace is > valuable. That means we should look for signal handlers before looking > for CFI. For NPTL that value judgement would fall the other way - not > having to special-case signal handlers is a clear win. > > Given the fact that it is desirable for GDB to know that it's dealing > with a signal handler, I think the correct approach is to extend the > DWARF2 unwinder with a method to get the frame type, similar to what > we already do for pre-initializing the register state. > > I'll see if I can come up with a patch for you to test. Had any time for this, Mark? If not, I can try it. I think this patch is very important for 6.3. -- Daniel Jacobowitz