unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
Cc: emacs-devel@gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: Re: gud breakage: ^done,changelist=[]
Date: Sat, 30 Oct 2004 08:48:55 +1300	[thread overview]
Message-ID: <16770.40615.484276.300510@farnswood.snap.net.nz> (raw)
In-Reply-To: <m3fz40mkix.fsf@kfs-l.imdomain.dk>


 > > So, in the short term, with care (albeit tedious), this problem should be
 > > avoidable.
 > 
 > The above "mistake" is easy to make.

When debugging programs which don't read from standard input, such as Emacs
(and Lilypond?) the conditional clause in gdb-send can be removed:

(defun gdb-send (proc string)
  "A comint send filter for gdb.
This filter may simply queue output for a later time."
    (gdb-enqueue-input (concat string "\n")))

This should eliminate the problem for such programs but will eventually hang
for those expecting input.

The general problem seems intractable because Emacs has no way of knowing if
input is going to gdb or the inferior. The original code (gdba.el) got round
the problem by always using a separate buffer for program input. Perhaps I
should do what Stefan suggested a while ago and create a lisp command,
gdb-resync, so that the user can recover control during a debug session and
all is not lost.

Nick

  reply	other threads:[~2004-10-29 19:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18  9:37 gud breakage: ^done,changelist=[] Jan Nieuwenhuizen
2004-10-18 11:17 ` Nick Roberts
2004-10-18 12:17   ` Jan Nieuwenhuizen
2004-10-18 12:58     ` Kim F. Storm
2004-10-18 21:22       ` Jan Nieuwenhuizen
2004-10-19  2:20         ` Nick Roberts
2004-10-27  8:43       ` Nick Roberts
2004-10-27 12:07         ` Kim F. Storm
2004-10-29 19:48           ` Nick Roberts [this message]
2004-10-29 20:34             ` Jan Nieuwenhuizen
2004-10-29 21:45             ` Stefan
2004-10-28  7:59         ` Jan Nieuwenhuizen
2004-10-19  6:13 ` Richard Stallman

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=16770.40615.484276.300510@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=emacs-devel@gnu.org \
    --cc=janneke@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).