From: William Xu <william.xwl@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: gdb mode with gdb command from the docker
Date: Mon, 19 Oct 2020 08:39:08 +0200 [thread overview]
Message-ID: <m2ft6ayb1v.fsf@gmail.com> (raw)
In-Reply-To: CAP_d_8UBVSnOXUwNyM2_PbcZSv5MmZDSzE=wxE4HodFDGJ3qaA@mail.gmail.com
Yuri Khan <yuri.v.khan@gmail.com> writes:
> On Sun, 18 Oct 2020 at 18:08, William Xu <william.xwl@gmail.com> wrote:
>
>> I'm trying to use gdb mode with the gdb command from the docker image.
>> So i defined a wrapper of gdb from docker:
>>
>> ---------------------------------8<-------------------------------------
>> #!/bin/sh
>> arg="$@"
>> docker exec -i myproject gdb -i=mi ${arg}
>> ---------------------------------8<-------------------------------------
>>
>> Then invoke the gdb with: (gdb "/path/gdbWrapper"). The *gud* buffer
>> can be created successfully. The executable file can be loaded OK,
>> however, it reports some tty error while trying to run the executable:
>
> Does giving the -t option to ‘docker exec’ help in any way? (I did not
> test this; just a hunch because something seems to expect a tty and -t
> causes docker to allocate one.)
I tried that earlier (changed it to: docker exec -it ... ), it seems making the situation worse, : )
Beside the same error showing up when running it, I also found this new
error at the beginning of the buffer:
Error: you did not specify -i=mi on GDB's command line!
--
William
prev parent reply other threads:[~2020-10-19 6:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 15:08 gdb mode with gdb command from the docker William Xu
2020-10-18 15:57 ` Eli Zaretskii
2020-10-18 18:18 ` William Xu
2020-10-18 18:35 ` Eli Zaretskii
2020-10-20 19:54 ` William Xu
2020-10-21 16:10 ` Eli Zaretskii
2020-10-22 18:41 ` William Xu
2020-10-22 18:49 ` Eli Zaretskii
2020-10-22 19:27 ` William Xu
2020-10-18 18:48 ` Yuri Khan
2020-10-18 19:00 ` otadmor
2020-10-19 6:41 ` William Xu
2020-10-19 6:39 ` William Xu [this message]
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=m2ft6ayb1v.fsf@gmail.com \
--to=william.xwl@gmail.com \
--cc=help-gnu-emacs@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.
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).