From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: other weird gdb-mi problems Date: Thu, 27 Aug 2009 18:42:23 +0900 Message-ID: References: <83vdkacx2k.fsf@gnu.org> <19093.50389.972379.110708@totara.tehura.co.nz> <878wh6gh48.fsf@catnip.gol.com> <19094.4394.535184.630878@totara.tehura.co.nz> Reply-To: Miles Bader NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1251366586 12273 80.91.229.12 (27 Aug 2009 09:49:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 27 Aug 2009 09:49:46 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org, Dmitry Dzhus To: nickrob@snap.net.nz (Nick Roberts) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Aug 27 11:49:39 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 1Mgbbu-0002OU-RA for ged-emacs-devel@m.gmane.org; Thu, 27 Aug 2009 11:49:39 +0200 Original-Received: from localhost ([127.0.0.1]:58555 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgbbt-0002KQ-TG for ged-emacs-devel@m.gmane.org; Thu, 27 Aug 2009 05:49:37 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mgbbk-0002In-Ul for emacs-devel@gnu.org; Thu, 27 Aug 2009 05:49:29 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mgbbf-0002FV-JF for emacs-devel@gnu.org; Thu, 27 Aug 2009 05:49:27 -0400 Original-Received: from [199.232.76.173] (port=46693 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mgbbf-0002FS-EK for emacs-devel@gnu.org; Thu, 27 Aug 2009 05:49:23 -0400 Original-Received: from tyo201.gate.nec.co.jp ([202.32.8.193]:61347) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MgbUx-0007Ug-UD; Thu, 27 Aug 2009 05:42:28 -0400 Original-Received: from relay11.aps.necel.com ([10.29.19.46]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id n7R9gO4l014210; Thu, 27 Aug 2009 18:42:24 +0900 (JST) Original-Received: from relay21.aps.necel.com ([10.29.19.20] [10.29.19.20]) by relay11.aps.necel.com with ESMTP; Thu, 27 Aug 2009 18:42:24 +0900 Original-Received: from dhlpc061 ([10.114.112.173] [10.114.112.173]) by relay21.aps.necel.com with ESMTP; Thu, 27 Aug 2009 18:42:24 +0900 Original-Received: by dhlpc061 (Postfix, from userid 31295) id 8060F52E1EE; Thu, 27 Aug 2009 18:42:24 +0900 (JST) System-Type: x86_64-unknown-linux-gnu Blat: Foop In-Reply-To: <19094.4394.535184.630878@totara.tehura.co.nz> (Nick Roberts's message of "Thu, 27 Aug 2009 16:52:58 +1200") Original-Lines: 46 X-detected-operating-system: by monty-python.gnu.org: Solaris 8 (1) 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:114679 Archived-At: nickrob@snap.net.nz (Nick Roberts) writes: > > p.s. What about emacs showing the wrong source file? > > which resets the frame. The change below seems to fix this for the problem > you reported with "up" and "down" by just specifying the thread, Thanks, that patch fixes both problems for me. BTW, a few other things I noticed while testing that: (1) Calling a program function from gdb to display various info; these no longer seems to work. E.g. if I do: "call dump_loc(SOME_VAR)" where the "dump_loc" function just prints some stuff about SOME_VAR to stdout (and then flushes stdout). In previous versions of gdb this worked great, but now it doesn't. This is actually kinda important, because it's a very commonly used technique to add gdb debugging hooks into programs... I thought maybe this had something to do with the "*input/output ...*" buffer which is now getting used, but the output didn't show up there either. (2) It display breakpoint icon in the margin, instead of in the fringe, if I have the "fringe-style" set to `half'. I guess maybe it's trying to ensure that the icon it fits in the space available, and indeed, there's like a single pixel chopped off one edge if I force it (by setting half-margin-mode _after_ setting the breakpoint). However, having the margins are much more annoying than slightly truncated icons (especially since the icon is essentially, a red blob), so it would be nice if it were less eager about doing this, or tried to substitute a smaller icon in such a case, or something. Thanks, -Miles -- "Suppose He doesn't give a shit? Suppose there is a God but He just doesn't give a shit?" [George Carlin]