unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: 9767@debbugs.gnu.org
Subject: bug#9767: 24.0.90; gdb initialization on Cygwin
Date: Sun, 16 Oct 2011 19:08:32 -0400	[thread overview]
Message-ID: <4E9B63F0.5040409@cornell.edu> (raw)
In-Reply-To: <4E9B0033.2070506@cornell.edu>

On 10/16/2011 12:02 PM, Ken Brown wrote:
> When I start a debugging session with M-x gdb, initialization doesn't
> appear to complete. I don't get the "(gdb)" prompt, and the mode line
> continues to say "initializing". If I press Return, I get the prompt
> and the mode line changes to "ready". Everything works fine after that.
> This seems Cygwin-specific; it doesn't happen on GNU/Linux.
>
> I've checked that all the strings that emacs sends to gdb during
> initialization (via gdb-input) do in fact get sent. And I've tried
> sending those same strings to gdb outside of emacs (except for
> "-inferior-tty-set..."), and nothing strange happened. In particular, I
> did have a "(gdb)" prompt at each stage.

Further info: It seems that initialization is actually completing, but 
for some reason the buffer is not being redisplayed.  To test this, I 
inserted (sit-for .1) at the end of gdb-update to force redisplay, and 
that solved the problem.  Unless someone who understands redisplay can 
figure out why redisplay isn't happening on Cygwin, I'm inclined to 
apply the following patch:

=== modified file 'lisp/progmodes/gdb-mi.el'
--- lisp/progmodes/gdb-mi.el    2011-10-06 16:11:38 +0000
+++ lisp/progmodes/gdb-mi.el    2011-10-16 23:04:28 +0000
@@ -1726,7 +1726,8 @@
      (gdb-force-mode-line-update
       (propertize "initializing..." 'face font-lock-variable-name-face))
      (gdb-init-1)
-    (setq gdb-first-prompt nil))
+    (setq gdb-first-prompt nil)
+    (if (eq system-type 'cygwin) (sit-for .1)))

    (gdb-get-main-selected-frame)
    ;; We may need to update gdb-threads-list so we can use

Would this be reasonable?

Ken





  reply	other threads:[~2011-10-16 23:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-16 16:02 bug#9767: 24.0.90; gdb initialization on Cygwin Ken Brown
2011-10-16 23:08 ` Ken Brown [this message]
2011-10-17  5:39   ` Eli Zaretskii
2011-10-19 20:00     ` Ken Brown
2011-10-19 20:26       ` Eli Zaretskii
2011-10-19 20:43         ` Ken Brown
2011-10-19 21:03           ` Andreas Schwab
2011-10-19 22:02             ` Eli Zaretskii
2011-10-20  2:11               ` Ken Brown
2011-10-21 20:47                 ` Ken Brown
2011-10-21 22:15                   ` Eli Zaretskii
2011-10-22  9:51                     ` Ken Brown
2011-10-22 20:58                       ` Ken Brown
2011-10-23 21:59                         ` Ken Brown
2011-10-21 22:24                   ` Stefan Monnier
2011-10-22  9:47                     ` Ken Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E9B63F0.5040409@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=9767@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).