From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: Re: New function for gdb-ui.el? Date: Wed, 26 Oct 2005 12:00:51 +1300 Message-ID: <17246.47395.926373.263704@kahikatea.snap.net.nz> References: <17243.21638.138477.436126@kahikatea.snap.net.nz> <17244.34246.93773.562211@kahikatea.snap.net.nz> <17245.17271.523511.307415@kahikatea.snap.net.nz> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1130281373 16682 80.91.229.2 (25 Oct 2005 23:02:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 25 Oct 2005 23:02:53 +0000 (UTC) Cc: ich@frank-schmitt.net, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Oct 26 01:02:40 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EUXmk-00057j-TK for ged-emacs-devel@m.gmane.org; Wed, 26 Oct 2005 01:00:51 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EUXmk-0007Fh-CM for ged-emacs-devel@m.gmane.org; Tue, 25 Oct 2005 19:00:50 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EUXmO-0007FX-0w for emacs-devel@gnu.org; Tue, 25 Oct 2005 19:00:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EUXmM-0007FI-Ai for emacs-devel@gnu.org; Tue, 25 Oct 2005 19:00:27 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EUXmL-0007FF-QJ for emacs-devel@gnu.org; Tue, 25 Oct 2005 19:00:25 -0400 Original-Received: from [202.37.101.8] (helo=viper.snap.net.nz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1EUXmD-0002e6-Fx; Tue, 25 Oct 2005 19:00:17 -0400 Original-Received: from kahikatea.snap.net.nz (p14-tnt2.snap.net.nz [202.124.108.14]) by viper.snap.net.nz (Postfix) with ESMTP id 0D8D1731237; Wed, 26 Oct 2005 12:00:07 +1300 (NZDT) Original-Received: by kahikatea.snap.net.nz (Postfix, from userid 500) id 513318402; Wed, 26 Oct 2005 12:00:52 +1300 (NZDT) Original-To: rms@gnu.org In-Reply-To: X-Mailer: VM 7.19 under Emacs 22.0.50.23 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:44877 Archived-At: > > To move to another file usually means moving to another frame, and > > that's not the job of `until'. This command should refuse > > to move to another frame. > > Yes, you're right. > > Actually, now I am not sure what I said is true. Maybe `until' just > sets a temporary breakpoint and continues. If so, it would actually > "work" even if you specify a line in a different function. The manual says: GDB> Continue running your program until either the specified location GDB> is reached, or the current stack frame returns. (actually, it should say *selected* stack frame returns) As Eli says, there is now another command called "advance". I think this has the behaviour you are talking about: GDB> ...the target location doesn't have to be in the same frame as the GDB> current one. > > But there is an exception: when a function in one file is inlined in > > another. In that case, shouldn't this command work? > > If I try it, it doesn't seem to work. Even if it, I'm not sure how we > would make use of it. > > If it doesn't work, maybe that is a flaw in GDB. It OUGHT to be > possible to proceed to a specific line in the code another function > that was inlined into this function. > > Would you like to raise that is with bug-gdb and cc me? The problem is that the documentation just talks about being able to skip over recursive functions and doesn't mention inline functions. So I'm not sure that they would see it as a bug. Nick