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: gdbui hang Date: Tue, 11 May 2004 22:27:08 +0100 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <16545.17708.52927.395469@nick.uklinux.net> 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> <20040511210854.GB8144@fencepost> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1084312579 21206 80.91.224.253 (11 May 2004 21:56:19 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 May 2004 21:56:19 +0000 (UTC) Cc: Stefan Monnier , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 11 23:55:57 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 1BNfEC-0004to-00 for ; Tue, 11 May 2004 23:55:56 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNfEC-0006R0-00 for ; Tue, 11 May 2004 23:55:56 +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 1BNfC6-0000bx-QK for emacs-devel@quimby.gnus.org; Tue, 11 May 2004 17:53:46 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNfBv-0000Zz-PJ for emacs-devel@gnu.org; Tue, 11 May 2004 17:53:35 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNf4a-00070O-As for emacs-devel@gnu.org; Tue, 11 May 2004 17:46:31 -0400 Original-Received: from [194.247.51.210] (helo=nick.uklinux.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNems-0002SC-Cq; Tue, 11 May 2004 17:27:43 -0400 Original-Received: by nick.uklinux.net (Postfix, from userid 501) id 925F875FDF; Tue, 11 May 2004 22:27:08 +0100 (BST) Original-To: Miles Bader In-Reply-To: <20040511210854.GB8144@fencepost> X-Mailer: VM 6.97 under Emacs 21.2.1 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:23183 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23183 > 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? If they are repeatable, you could set the variable gdb-enable-debug-log (which records the transactions between gdb and emacs) to t, trigger the bug and post the value of gdb-debug-log to emacs-devel. If they're not repeatable, maybe you could start with gdb-enable-debug-log set to t and post the last part of gdb-debug-log to emacs-devel. I've not tried this though, and gdb-debug-log might get very large and slow things down. Nick