public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: gdb@sourceware.org
Subject: Interactive behavior of GDB run from Emacs on Windows
Date: Thu, 19 Apr 2012 15:46:00 -0000	[thread overview]
Message-ID: <83vckviv3b.fsf@gnu.org> (raw)

There's an annoying difference between GDB behavior when launched by
Emacs GUD on Windows and on Posix platforms.  AFAIU, the difference is
explained by the fact that on Posix platforms the communications
between Emacs and GDB are done via a pty, whereas on Windows Emacs
uses pipes.  Therefore, on Unix GDB behaves as if its standard handles
were connected to a terminal, while on Windows it doesn't.

This causes some prompts, like the one GDB displays after "commands"
etc., not to show on Windows, and also rears its ugly head in other
situations.

What would be the best way to solve this annoyance?  One possibility I
thought of would be to have a "set something" option which Emacs would
cram down the pipe early on, that will force GDB to behave as if it
were talking to a terminal (we already have a similar hack for
Insight).  Would that be acceptable, and is it easily and cleanly
doable?  (I don't know enough about the ser-*.c stuff to decide
whether there could be any pitfalls along this route.)

TIA

             reply	other threads:[~2012-04-19 15:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19 15:46 Eli Zaretskii [this message]
2012-04-19 15:49 ` Joel Brobecker
2012-04-19 16:11   ` Eli Zaretskii
2012-04-19 16:17     ` GDB/MI and ">" prompts (was: Interactive behavior of GDB run from Emacs on Windows) Eli Zaretskii
2012-04-19 18:53       ` Joel Brobecker
2012-04-19 19:25         ` GDB/MI and ">" prompts Eli Zaretskii

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=83vckviv3b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.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.
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).