From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.devel Subject: Re: gdba probs Date: Sun, 15 Dec 2002 00:36:02 +0000 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <15867.52850.157380.627084@nick.uklinux.net> References: <15855.47556.171128.631234@nick.uklinux.net> <200212052149.gB5LnZ504967@rum.cs.yale.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1039912867 27299 80.91.224.249 (15 Dec 2002 00:41:07 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 15 Dec 2002 00:41:07 +0000 (UTC) Cc: emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18NMq9-00075v-00 for ; Sun, 15 Dec 2002 01:41:05 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 18NN2t-0006se-00 for ; Sun, 15 Dec 2002 01:54:15 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18NMo7-0005jW-03 for emacs-devel@quimby.gnus.org; Sat, 14 Dec 2002 19:38:59 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18NMnX-0005XE-00 for emacs-devel@gnu.org; Sat, 14 Dec 2002 19:38:23 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18NMnR-0005WR-00 for emacs-devel@gnu.org; Sat, 14 Dec 2002 19:38:19 -0500 Original-Received: from bts-0462.dialup.zetnet.co.uk ([194.247.49.206] helo=nick.uklinux.net) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18NMnQ-0005RC-00; Sat, 14 Dec 2002 19:38:17 -0500 Original-Received: by nick.uklinux.net (Postfix, from userid 501) id D5E9876037; Sun, 15 Dec 2002 00:36:02 +0000 (GMT) Original-To: "Stefan Monnier" , miles@gnu.org In-Reply-To: <200212052149.gB5LnZ504967@rum.cs.yale.edu> X-Mailer: VM 6.97 under Emacs 21.3.50.2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:10140 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:10140 Stefan Monnier writes: > I have no idea what this entails, but maybe it is related to another > wish of mine: to make it usable when running "gdb --fullname foo". > Right now, it seems that if gdb is not started with "--annotate=2" > gdba just "freezes" (typing stuff at gdb prompt leads nowhere). I've looked at it now. It "freezes" because when a gdb command is typed in the GUD buffer goes onto the queue (C-h v gdb-input-queue). It goes on the input queue because gdb-instance-prompting is nil therefore thinks its not ready for input. gdb-instance-prompting is nil because it hasn't received the prompt annotation. It hasn't received the prompt annotation because its been called with "--fullname". > > > > @@ -2344,6 +2347,42 @@ > > > > > > > > (defun gud-filter (proc string) > > > > ;; Here's where the actual buffer insertion is done > > > > + (when (and gud-first-time (string-match > > > > + "\n\032\032[a-z]" string)) > > > > > > What if DBX outputs this same sequence? > > > > You take the patch too literally. It should have something like: > > > > (string-match "\n\032\032pre-prompt\|\n\032\032breakpoints-invalid" string) > And? Same thing: some other debugger might use the exact same sequence. > Better put the test in gud-gdb-marker-filter so there's not ambiguity > and so the generic part of the code stays cleaner. I see now that "^Z^Z" is some kind of universal marker, I had thought it was GDB specific. > Better put the test in gud-gdb-marker-filter so there's not ambiguity > and so the generic part of the code stays cleaner. > ... It might be easier to approach it from the other end i.e add an annotation rule for gdb-output-burst to accommodate "--fullname". > The ultimate goal is to merge M-x gdb and M-x gdba, but it doesn't > have to be done in a single step. I think the first step is to make > sure that both work (maybe with quirks) regardless of whether > --annotate=2 was used or not. I think I understand now. I'll go away and think about it. Miles Bader writes : > into a separate function to avoid cluttering up gud-filter, something > like `gdba-take-over-process' or something. It could even be an > autoloaded function in gdb-ui.el. ^^^^^^^^^^ So gdb-ui.el wouldn't get loaded unless gdb was invoked with annotations, right? Thats a good point, I hadn't thought of that. Nick