unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Roland Coeurjoly <rolandcoeurjoly@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 40279@debbugs.gnu.org
Subject: bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!
Date: Mon, 26 Oct 2020 22:07:16 +0100	[thread overview]
Message-ID: <CAMdauZpMdZrieM3SY0rHjPCFvhB6vDpro0j+ksa-n1PKXoffQA@mail.gmail.com> (raw)
In-Reply-To: <87a6w8vh0j.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

>
> Like I said, I know nothing about Docker, but my totally uninformed
> guess would be that something in that command line mangles the output
> from gdb, somehow, so that Emacs is no longer able to parse it.


Yes, that seems to be the case.

I posted this in stackoverflow here:
https://stackoverflow.com/questions/60112087/error-you-did-not-specify-i-mi-on-gdbs-command-line-in-docker

Would that be ok just to provide the link?

On Mon, Oct 26, 2020 at 10:01 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Roland Coeurjoly <rolandcoeurjoly@gmail.com> writes:
>
> > Yes, the problem is that it doesn't split the frame in different
> windows, and nothing
> > good happens.
> >
> > I need to run gdb inside Docker, and I have a strong preference for the
> interface
> > provided by emacs.
> >
> > When doing M-x gdb, I enter "docker-compose -f
> > ~/docker-services/dev/docker-compose.yml exec dev_rhel7 bash -c "gdb
> -i=mi"",
> > and then it shows me the following message.
>
> Like I said, I know nothing about Docker, but my totally uninformed
> guess would be that something in that command line mangles the output
> from gdb, somehow, so that Emacs is no longer able to parse it.
>
> It's hard to tell, since you're posting via Gmail, as HTML, and the
> output examples you include have been mangled beyond recognition.
>
> Perhaps try including them as attachments?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: Type: text/html, Size: 2397 bytes --]

  reply	other threads:[~2020-10-26 21:07 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 [this message]
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
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=CAMdauZpMdZrieM3SY0rHjPCFvhB6vDpro0j+ksa-n1PKXoffQA@mail.gmail.com \
    --to=rolandcoeurjoly@gmail.com \
    --cc=40279@debbugs.gnu.org \
    --cc=larsi@gnus.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).