GNU bug report logs - #40279
26.3; Error: you did not specify -i=mi on GDB's command line!

Previous Next

Package: emacs;

Reported by: Roland Coeurjoly <rolandcoeurjoly <at> gmail.com>

Date: Sun, 29 Mar 2020 17:12:02 UTC

Severity: normal

Tags: moreinfo

Merged with 28309

Found in version 26.3

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: William Xu <william.xwl <at> gmail.com>
Cc: 40279 <at> 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

> From: William Xu <william.xwl <at> gmail.com>
> Date: Tue, 27 Oct 2020 21:04:55 +0100
> 
> Lars Ingebrigtsen <larsi <at> 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.
This bug report was last modified 4 years and 202 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.