From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: 9767@debbugs.gnu.org
Subject: bug#9767: 24.0.90; gdb initialization on Cygwin
Date: Mon, 17 Oct 2011 01:39:19 -0400 [thread overview]
Message-ID: <E1RFfux-0003wt-EL@fencepost.gnu.org> (raw)
In-Reply-To: <4E9B63F0.5040409@cornell.edu> (message from Ken Brown on Sun, 16 Oct 2011 19:08:32 -0400)
> Date: Sun, 16 Oct 2011 19:08:32 -0400
> From: Ken Brown <kbrown@cornell.edu>
>
> 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:
My crystal ball says that redisplay isn't happening because Emacs
doesn't know that the GDB prompt has arrived. The call to sit-for
causes Emacs to check its input descriptors, "discovering" that there
is input.
Please look around in wait_reading_process_output, and see what is
going on there, before and after the call to sit-for. In particular,
does the call to `select' report that input has arrived from GDB?
> === 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?
I think it's not going to solve the real problem. If Emacs misses
some of the output arriving from GDB, it will miss it again under
similar circumstances.
next prev parent reply other threads:[~2011-10-17 5:39 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
2011-10-17 5:39 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1RFfux-0003wt-EL@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9767@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.