[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!
From: |
Lars Ingebrigtsen |
Subject: |
bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line! |
Date: |
Fri, 30 Oct 2020 13:19:04 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
William Xu <william.xwl@gmail.com> writes:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
>> Does the `M-x gud-gdb' command work OK in the Docker use case? That one
>> doesn't have a separate socket for the I/O.
>
> I just tested it, yes, it works well without my change.
I think it's probably not feasible to get the gdb-mi interface working
within Docker (with Emacs on the outside), so I think the right fix here
is to just make the error message less sure of itself.
I've now done this in Emacs 28.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, Lars Ingebrigtsen, 2020/10/26
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, Roland Coeurjoly, 2020/10/26
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, William Xu, 2020/10/27
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, Lars Ingebrigtsen, 2020/10/27
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, William Xu, 2020/10/27
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, Lars Ingebrigtsen, 2020/10/27
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, William Xu, 2020/10/28
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!,
Lars Ingebrigtsen <=
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, William Xu, 2020/10/30
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, Eli Zaretskii, 2020/10/27
- bug#40279: 26.3; Error: you did not specify -i=mi on GDB's command line!, Eli Zaretskii, 2020/10/27