Re: [PATCH v2 0/2] MI: Add new command -complete

Eli Zaretskii
2019-03-06T15:45:05Z

> From: Jan Vrany <jan.vrany@fit.cvut.cz>
> Cc: gdb-patches@sourceware.org, "gdb@sourceware.org" <gdb@sourceware.org>
> Date: Wed, 06 Mar 2019 15:09:33 +0000
>
> > > 1) Completion CLI is AFAIK implemented using readline which has problems
> > > working over pipes. Actually, I never got CLI working satisfactorily
> > > on Windows even when I just run GDB "normally" from Windows command shell (`cmd.exe`),
> > > let alone over pipes or alike.
> >
> > Curious. AFAIK native Windows gdb over cmd.exe should work fine.
>
> Maybe I just don't know how to compile it properly. I have just compiled
> fresh c3734e093aab1ce from git (only with this patch
> https://sourceware.org/ml/gdb-patches/2018-10/msg00614.html to make it compile
> with Python 3) using using MSYS2 MINGW64 toolchain on Windows 10.
> This is the exact configure command:
>
> bash ../configure --build=x86_64-w64-mingw32 --disable-werror --with-guile=no --with-python=C:\msys64\mingw64\bin\python3 --enable-targets="i686-w64-mingw32,x86_64-w64-mingw32"
>
> Completion by tab seem to work.
>
> Backspace practially does not, it deletes the character in the line
> buffer (presumably) but not on the screen. Instead, it moves the caret
> one character on the right. Therefore what use see on the screen is not
> what it sent to GDB when she presses enter.
>
> Moving cursor by left arrow followed by typing has similar issues.
> Same for delete. Same for pressing Ctrl-R for searching the history.

How did you invoke GDB from cmd.exe, to make these problems appear?
Can you show your exact invocation command line?