From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: gdbui hang Date: Tue, 11 May 2004 17:08:54 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <20040511210854.GB8144@fencepost> References: <16543.48205.566122.924505@nick.uklinux.net> <87ekpsrvvh.fsf-monnier+emacs@gnu.org> <16543.52509.961888.971742@nick.uklinux.net> <20040511124932.GA2459@fencepost> <16545.14031.598931.771041@nick.uklinux.net> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084310017 26335 80.91.224.253 (11 May 2004 21:13:37 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 May 2004 21:13:37 +0000 (UTC) Cc: emacs-devel@gnu.org, Stefan Monnier , Miles Bader Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 11 23:13:30 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNeZ8-0001wk-00 for ; Tue, 11 May 2004 23:13:30 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNeZ7-0005TW-00 for ; Tue, 11 May 2004 23:13:30 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNeXv-0006RJ-US for emacs-devel@quimby.gnus.org; Tue, 11 May 2004 17:12:15 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNeWf-00068c-TG for emacs-devel@gnu.org; Tue, 11 May 2004 17:10:58 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNeUh-0005Yq-Cn for emacs-devel@gnu.org; Tue, 11 May 2004 17:09:26 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNeUg-0005YI-Ec for emacs-devel@gnu.org; Tue, 11 May 2004 17:08:54 -0400 Original-Received: from miles by fencepost.gnu.org with local (Exim 4.34) id 1BNeUg-0003Fc-5r; Tue, 11 May 2004 17:08:54 -0400 Original-To: Nick Roberts Content-Disposition: inline In-Reply-To: <16545.14031.598931.771041@nick.uklinux.net> User-Agent: Mutt/1.3.28i Blat: Foop X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23179 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23179 On Tue, May 11, 2004 at 09:25:51PM +0100, Nick Roberts wrote: > > The new gdbui mode seems to get wedged in these unrecoverable states way > > too often, and seems way too fragile... (with traditional gdb mode, > > hitting C-g a few times and then C-c C-c a few times was usually enough > > to get you back into some known state). > > For each GDB command the user types, it runs several behind the users back to > keep Emacs informed about the status of the program being debugged. This > requires careful co-ordination and will take just take time to iron out the > bugs. I can only suggest that you submit a bug report for each case. Yes, I fully understand your dilemna, but the bugs in gdbui typically seem pretty hard to describe in a useful way -- often it just hangs, and won't unhang -- and are not easily repeatable. Is there some internal state that be useful to quote in a bug report? Even better, how about a dump-gdbui-internal-state command that could be used when sending a bug report? Thanks, -Miles -- P.S. All information contained in the above letter is false, for reasons of military security.