From: William Xu <william.xwl@gmail.com>
To: 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 19:36:50 +0100 [thread overview]
Message-ID: <m2pn53cy7x.fsf@gmail.com> (raw)
In-Reply-To: <CAMdauZrfOZk+dOTfu2-cqYs0g1Rbn5=BL6stLfeBuFniBa_vKQ@mail.gmail.com>
Roland Coeurjoly <rolandcoeurjoly@gmail.com> writes:
> From the previous test I deduce that it is an issue of emacs, not
> Docker.
I recently tried to setup calling gdb from docker as well, I also got
some weird errors. Eventually I'm able to make it work by disabling the
I/O separation (via "-inferior-tty-set") done by gdb mode.
Root cause seems that emacs allocates an inferior tty (for I/O
separation in gdb) for the *host*, which of course is not known to
docker gdb. I'm not really sure how it should be properly fixed.
This is my setup, I wrap around the gdb docker in a script:
https://lists.gnu.org/archive/html/help-gnu-emacs/2020-10/msg00311.html
This is the change I have to make:
https://lists.gnu.org/archive/html/help-gnu-emacs/2020-10/msg00369.html
P.S. I had hope on tramp remote gdb, but there are other issues... :(
https://lists.gnu.org/archive/html/bug-gnu-emacs/2020-10/msg01839.html
--
William
next prev parent reply other threads:[~2020-10-27 18:36 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 [this message]
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
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=m2pn53cy7x.fsf@gmail.com \
--to=william.xwl@gmail.com \
--cc=40279@debbugs.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).