From: Eli Zaretskii <eliz@gnu.org>
To: William Xu <william.xwl@gmail.com>
Cc: 40279@debbugs.gnu.org
Subject: bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!
Date: Tue, 27 Oct 2020 22:20:44 +0200 [thread overview]
Message-ID: <831rhje7z7.fsf@gnu.org> (raw)
In-Reply-To: <m2imavcu54.fsf@gmail.com> (message from William Xu on Tue, 27 Oct 2020 21:04:55 +0100)
> From: William Xu <william.xwl@gmail.com>
> Date: Tue, 27 Oct 2020 21:04:55 +0100
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > And as far as I can tell, gdb runs just fine without it, even on
> > GNU/Linux?
>
> Without that, the gdb commands and program I/O are mixed together in the
> same buffer, so "*input/output of...*" window in gdb-many-windows will
> be empty.
>
> It is mostly useful if there is a lot of I/O from the program. It makes
> it easier to inspect only the program I/O in that separated buffer.
No, it's useful even if the program does only a small amount of I/O,
because running GDB in the default mode on GNU/Linux lets you run the
program in the non-stop mode, where GDB and the program run in
parallel -- in that case if they both output stuff to the same file
descriptor, you will get an illegible mess.
next prev parent reply other threads:[~2020-10-27 20:20 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 [this message]
2020-10-27 20:09 ` Eli Zaretskii
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=831rhje7z7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=40279@debbugs.gnu.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).