From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7404 invoked by alias); 17 Apr 2003 20:50:02 -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 7378 invoked from network); 17 Apr 2003 20:50:01 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 17 Apr 2003 20:50: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 196GKd-0002RC-00; Thu, 17 Apr 2003 15:50:07 -0500 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 196GKQ-0000t9-00; Thu, 17 Apr 2003 16:49:54 -0400 Date: Thu, 17 Apr 2003 20:50:00 -0000 From: Daniel Jacobowitz To: Doug Evans Cc: Matt Thomas , Michael Snyder , gdb@sources.redhat.com Subject: Re: breakpoint commands and finish Message-ID: <20030417204953.GA26080@nevyn.them.org> Mail-Followup-To: Doug Evans , Matt Thomas , Michael Snyder , gdb@sources.redhat.com References: <5.1.1.6.2.20030414135022.04175790@3am-software.com> <5.1.1.6.2.20030417114351.04b179c0@3am-software.com> <20030417201909.GA2867@nevyn.them.org> <16031.4562.644834.479261@casey.transmeta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <16031.4562.644834.479261@casey.transmeta.com> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-04/txt/msg00205.txt.bz2 On Thu, Apr 17, 2003 at 01:42:58PM -0700, Doug Evans wrote: > Daniel Jacobowitz writes: > > > rbreak (or ebreak). I find I often was to place a breakpoint at the > > > end of a function; it'd be nice if gdb could do that automaticly. > > > > It's too darned hard :) Debug info does not represent the exit point > > of the function. It's not always at the end; modern gcc's can emit > > multiple exit edges, too. > > And if a tail-call optimization has been done, it gets even harder. > > OTOH, if one stops at the first instruction of a function, > presumably it'd then be easy to set a breakpoint at the return address. > I wonder if gdb's macro facility is sufficient to write a macro > that would make this almost user-friendly: it would set a > breakpoint at the start of the function (pre-prologue) then have > commands that first sets a tbreak breakpoint at the return address > and then continues. You couldn't already be in the function of > course (but if you were presumably you'd use "finish"). > > ? The macro facility isn't, but a command could be added to do this without much trouble. I would rather us discuss the semantics of commands lists containing commands which resume the inferior. There must be a more user-useful way to approach it than we do now. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer