From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: nickrob@snap.net.nz (Nick Roberts) Newsgroups: gmane.emacs.devel Subject: Re: other weird gdb-mi problems Date: Thu, 27 Aug 2009 11:27:17 +1200 Message-ID: <19093.50389.972379.110708@totara.tehura.co.nz> References: <83vdkacx2k.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1251336742 8798 80.91.229.12 (27 Aug 2009 01:32:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 27 Aug 2009 01:32:22 +0000 (UTC) Cc: emacs-devel@gnu.org, Miles Bader To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 27 03:32:15 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MgTqY-0002DY-6Q for ged-emacs-devel@m.gmane.org; Thu, 27 Aug 2009 03:32:14 +0200 Original-Received: from localhost ([127.0.0.1]:58424 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgTqX-0002Mu-FQ for ged-emacs-devel@m.gmane.org; Wed, 26 Aug 2009 21:32:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MgTqS-0002M7-T4 for emacs-devel@gnu.org; Wed, 26 Aug 2009 21:32:08 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MgTqN-0002Ii-8L for emacs-devel@gnu.org; Wed, 26 Aug 2009 21:32:08 -0400 Original-Received: from [199.232.76.173] (port=35803 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MgTqN-0002IY-26 for emacs-devel@gnu.org; Wed, 26 Aug 2009 21:32:03 -0400 Original-Received: from viper.snap.net.nz ([202.37.101.25]:60730) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MgTqH-00039Q-8K; Wed, 26 Aug 2009 21:31:57 -0400 Original-Received: from totara (unknown [123.255.30.200]) by viper.snap.net.nz (Postfix) with ESMTP id 6C6053DA4EC; Thu, 27 Aug 2009 11:27:19 +1200 (NZST) Original-Received: by totara (Postfix, from userid 1000) id 05B7DC164; Thu, 27 Aug 2009 11:27:18 +1200 (NZST) In-Reply-To: <83vdkacx2k.fsf@gnu.org> X-Mailer: VM 7.19 under Emacs 22.2.1 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 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:114650 Archived-At: > > ... wait a minute... why am I still at frame 1?! > > "down" is similarly weird: > > > > (gdb) down > > Bottom (innermost) frame selected; you cannot go down. > > Does this work correctly outside Emacs? (Sorry for asking such > obvious questions, but I thought it could be some genuine GDB problem > with inlined functions.) It's an Emacs problem. The CLI commands "up" and "down", don't emit any GDB/MI notifications so Emacs doen't know that the display needs updating. It could check the selected frame after every command but that seems inefficient. I have proposed using notifications for changes in state in the past on the GDB mailing list, e.g., http://sourceware.org/ml/gdb-patches/2008-04/msg00377.html but there hasn't been much interest. I think this is because many frontends don't use a console like the GUD buffer. -- Nick http://www.inet.net.nz/~nickrob