From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 40279@debbugs.gnu.org, william.xwl@gmail.com
Subject: bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!
Date: Tue, 27 Oct 2020 22:09:23 +0200 [thread overview]
Message-ID: <837drbe8i4.fsf@gnu.org> (raw)
In-Reply-To: <87pn53zdkw.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 27 Oct 2020 20:14:07 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Tue, 27 Oct 2020 20:14:07 +0100
> Cc: 40279@debbugs.gnu.org
>
> I tried looking at the VC logs to see what the point of the
> inferior-tty-set command was, but the only mention I found was:
>
> (gdb-inferior-io--init-proc): Don't send "-inferior-tty" command
> if the TTY name is nil or empty (which happens when communicating
> with the inferior via pipes, e.g. on MS-Windows).
>
> Which just disables it on Windows?
Yes. Because on Windows this is nothing but trouble.
> Hm... it was introduced below, but doesn't really say why.
>
> commit f30d612a7a628828baa7c333629a10295605291b
> Author: Chong Yidong <cyd@gnu.org>
> AuthorDate: Fri Apr 20 14:39:29 2012 +0800
>
> And as far as I can tell, gdb runs just fine without it, even on
> GNU/Linux?
It is needed to redirect the I/O of the program being debugged into a
separate buffer, so it doesn't get mixed with the interaction between
the user and GDB. gdb-many-windows creates, among others, a buffer
where the program's I/O is redirected.
next prev parent reply other threads:[~2020-10-27 20:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 7:21 bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line! Roland Coeurjoly
2020-10-26 14:19 ` Lars Ingebrigtsen
2020-10-26 20:31 ` Roland Coeurjoly
2020-10-26 21:01 ` Lars Ingebrigtsen
2020-10-26 21:07 ` Roland Coeurjoly
2020-10-27 7:46 ` Lars Ingebrigtsen
2020-10-27 18:36 ` William Xu
2020-10-27 19:14 ` Lars Ingebrigtsen
2020-10-27 20:04 ` William Xu
2020-10-27 20:11 ` Lars Ingebrigtsen
2020-10-28 19:48 ` William Xu
2020-10-30 12:19 ` Lars Ingebrigtsen
2020-10-30 16:29 ` William Xu
2020-10-27 20:20 ` Eli Zaretskii
2020-10-27 20:09 ` Eli Zaretskii [this message]
2020-11-03 18:52 ` William Xu
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=837drbe8i4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40279@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=william.xwl@gmail.com \
/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).