From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org
Subject: Re: gdb-ui
Date: Thu, 9 Mar 2006 10:23:30 +1300 [thread overview]
Message-ID: <17423.19282.313048.593168@kahikatea.snap.net.nz> (raw)
In-Reply-To: <m3irqo1y31.fsf@kfs-l.imdomain.dk>
> > If the program has no input, the user doesn't need to do anything new and
> > the change just helps to prevent gdb-ui getting confused.
>
> But in most cases, gdb-ui is not confused (right?)...
I'm not sure, it all depends on the nature of the program and how rapidly the
user types input. We've had a related thread before (Oct 2004,
gud breakage: ^done,changelist=[]) when I said:
Me> When debugging programs which don't read from standard input, such as Emacs
Me> (and Lilypond?) the conditional clause in gdb-send can be removed:
(on the value of gud-running)
Me> (defun gdb-send (proc string)
Me> "A comint send filter for gdb.
Me> This filter may simply queue output for a later time."
Me> (gdb-enqueue-input (concat string "\n")))
Me> This should eliminate the problem for such programs but will eventually
Me> hang for those expecting input.
So if you have patched your local version gdb-ui shouldn't confused, but this
is not a general solution.
> ...so how does the user
> know when gdb-ui _is_ confused so he should use M-return?
Perhaps I've not been clear. He should type M-return when the program is
prompting for input not when gdb-ui is confused.
> > C-return and C-M-return don't seem to be available on a terminal anyway.
> > Could I just use M-return?
>
> What about C-u RET ? Then we don't need another key.
It's a bit harder to type. Unlike C-return for CUA-mode, it would only be a
local binding (to the GUD buffer).
Nick
next prev parent reply other threads:[~2006-03-08 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 8:27 gdb-ui Nick Roberts
2006-03-08 10:05 ` gdb-ui Kim F. Storm
2006-03-08 12:15 ` gdb-ui Markus Gritsch
2006-03-08 13:08 ` gdb-ui Kim F. Storm
2006-03-08 19:24 ` gdb-ui Nick Roberts
2006-03-08 20:27 ` gdb-ui Kim F. Storm
2006-03-08 21:23 ` Nick Roberts [this message]
2006-03-09 8:20 ` gdb-ui Kim F. Storm
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=17423.19282.313048.593168@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=emacs-devel@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 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.