From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Nick Roberts Newsgroups: gmane.emacs.help Subject: Re: gud : Phase error in gdb-pre-prompt (got pre-emacs) Date: Fri, 27 Jun 2008 22:18:11 +1200 Message-ID: <18532.48739.801397.106683@kahikatea.snap.net.nz> References: <4864aa47$0$7552$9b4e6d93@newsspool1.arcor-online.net> 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 1214569247 17661 80.91.229.12 (27 Jun 2008 12:20:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 27 Jun 2008 12:20:47 +0000 (UTC) Cc: help-gnu-emacs@gnu.org To: Markus Grunwald Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jun 27 14:21:29 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1KCCxF-0006Wi-6a for geh-help-gnu-emacs@m.gmane.org; Fri, 27 Jun 2008 14:21:29 +0200 Original-Received: from localhost ([127.0.0.1]:52644 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KCCwO-0006zu-QA for geh-help-gnu-emacs@m.gmane.org; Fri, 27 Jun 2008 08:20:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KCCw0-0006y5-Gr for help-gnu-emacs@gnu.org; Fri, 27 Jun 2008 08:20:12 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KCCvy-0006w0-38 for help-gnu-emacs@gnu.org; Fri, 27 Jun 2008 08:20:11 -0400 Original-Received: from [199.232.76.173] (port=56463 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KCCvx-0006vu-RK for help-gnu-emacs@gnu.org; Fri, 27 Jun 2008 08:20:09 -0400 Original-Received: from viper.snap.net.nz ([202.37.101.25]:50265) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KCCvx-0007iT-O8 for help-gnu-emacs@gnu.org; Fri, 27 Jun 2008 08:20:10 -0400 Original-Received: from kahikatea.snap.net.nz (103.60.255.123.dynamic.snap.net.nz [123.255.60.103]) by viper.snap.net.nz (Postfix) with ESMTP id ED9BC3DA76C; Fri, 27 Jun 2008 22:18:23 +1200 (NZST) Original-Received: by kahikatea.snap.net.nz (Postfix, from userid 1000) id 7004E8FC6D; Fri, 27 Jun 2008 22:18:13 +1200 (NZST) Original-Newsgroups: gnu.emacs.help In-Reply-To: <4864aa47$0$7552$9b4e6d93@newsspool1.arcor-online.net> X-Mailer: VM 7.19 under Emacs 22.2.50.3 X-detected-kernel: by monty-python.gnu.org: Linux 2.4-2.6 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:55112 Archived-At: > I'm not lucky with my switch from emacs21 to GNU Emacs 22.2.1 > (i686-pc-linux-gnu, GTK+ Version 2.8.20): first emacs still hangs on > (next-buffer) (see earlier posting...), now gud is not working. > > What I did: > > >M-x gdb > >gdb --annotate=3 binary.bin > > gdb loads the binary, I get the gdb prompt. Then: > > Current directory is somewhere. > GNU gdb 6.6 > Copyright (C) 2006 Free Software Foundation, Inc. [...] > This GDB was configured as "i686-pc-linux-gnu"... Using host libthread_db > library "/lib/tls/i686/cmov/libthread_db.so.1". > (gdb) run > C-c C-c C-c C-c C-c C-c > > C-c C-c > C-c C-c C-c C-c What does it say within the square brackets in the mode-line of the GUD buffer _before_ you type `C-c C-c'? If it says "initializing..." then it might help to wait a bit longer until it says "ready" before typing the first command. There are several factors that might make this slow: 1) An executable that was created from a large number of files. 2) Using stabs debug format. 3) Using an old PC. If this is the problem I can post a patch that might speed things up but just turning off gud-tooltip-mode might help. If you still get an error after waiting for "ready": 1) Set gdb-enable-debug to t using M-x set-variable. 2) Do M-x gdb and enter "run" in the GUD buffer to get the error. 4) Post the value of gdb-debug-log (you can use `C-h v') to the list (or just to me if it's large). -- Nick http://www.inet.net.nz/~nickrob