From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10205 invoked by alias); 10 Oct 2002 19:11:15 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10130 invoked from network); 10 Oct 2002 19:11:01 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 10 Oct 2002 19:11:01 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17zjdr-0006pi-00; Thu, 10 Oct 2002 15:10:43 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17ziin-00051Q-00; Thu, 10 Oct 2002 15:11:45 -0400 Date: Thu, 10 Oct 2002 12:11:00 -0000 From: Daniel Jacobowitz To: Kevin Buettner Cc: gdb@sources.redhat.com Subject: Re: i386-linux signal backtraces broken Message-ID: <20021010191145.GA19287@nevyn.them.org> Mail-Followup-To: Kevin Buettner , gdb@sources.redhat.com References: <20021010184739.GA15971@nevyn.them.org> <1021010190606.ZM11731@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1021010190606.ZM11731@localhost.localdomain> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-10/txt/msg00098.txt.bz2 On Thu, Oct 10, 2002 at 12:06:06PM -0700, Kevin Buettner wrote: > On Oct 10, 2:47pm, Daniel Jacobowitz wrote: > > > We have two choices, that I see: > > - Call the code inspection functions always > > - Call the code inspection functions if the name is sigaction, taking > > advantage of the glibc implementation detail that sigaction is the > > only exported name for this function that I can see, and they are > > implemented right after it in the same file. > > > > Option (A) is a performance hit. Option (B) is, well, a little fragile. > > > > Thoughts? > > It sounds to me like option (A) is the way to go. How bad is the > performance hit? Hard to say, since I don't have any way to test GDB's reaction speed... it's going to mean at least one more read from target memory per frame in a backtrace, for instance. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer