Re: gdb mode with gdb command from the docker

[Eli Zaretskii]

> From: William Xu <william.xwl@gmail.com>
> Date: Thu, 22 Oct 2020 20:41:52 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > No, this setting is needed to separate the I/O device of the process
> > being debugged from that of GDB, so that we could redirect I/O of the
> > debuggee to a dedicated buffer used by "M-x gdb" to show interaction
> > with the program.
> 
> Can we at least add an option to disable the I/O separation, like
> gdb-disable-io-redirection? So that one can still have a working gdb,
> even if the I/O are mixed with gdb commands. So that I would still have
> the nice features of gdb modes, with which I can set breakpoints, follow
> line by line in the source buffer. That is already a huge improvement on
> the plain terminal gdb.

I don't understand why you need this.  Didn't you say that the problem
disappears if you use Yuri's advice?  Then why do we need any kludgey
changes in gdb-mi.el?

> In addition, I just noticed that tramp seems supporting such kind of
> remote debugging, from [[info:tramp#Remote processes][info:tramp#Remote 
> processes]]:
> 
> ,----
> | 5.5.5 Running a debugger on a remote host
> | -----------------------------------------
> | 
> | ‘gud.el’ provides a unified interface to symbolic debuggers (*note
> | (emacs)Debuggers::).  TRAMP can run debug on remote hosts by calling
> | ‘gdb’ with a remote file name:
> | 
> |      M-x gdb <RET>
> |      Run gdb (like this): gdb -i=mi /ssh:host:~/myprog <RET>
> `----
> 
> Only that when trying it out with ssh method, I got an error after the
> file is loaded. Should I report a bug for it?

Yes, please.