From: Eli Zaretskii <eliz@gnu.org>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: palves@redhat.com, tom@tromey.com, gdb-patches@sourceware.org,
gdb@sourceware.org
Subject: Re: [PATCH v2 0/2] MI: Add new command -complete
Date: Wed, 06 Mar 2019 15:45:00 -0000 [thread overview]
Message-ID: <83k1hcc8hv.fsf@gnu.org> (raw)
In-Reply-To: <825af91304d4a13bb6d599c16d68411fc6f37970.camel@fit.cvut.cz> (message from Jan Vrany on Wed, 06 Mar 2019 15:09:33 +0000)
> 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?
next prev parent reply other threads:[~2019-03-06 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87imynm3ia.fsf@tromey.com>
[not found] ` <20190128124101.26243-1-jan.vrany@fit.cvut.cz>
[not found] ` <87pnrmnolt.fsf@tromey.com>
2019-02-21 16:05 ` Jan Vrany
2019-02-26 19:49 ` Tom Tromey
2019-02-27 10:41 ` Jan Vrany
2019-02-27 20:41 ` Pedro Alves
2019-02-28 10:18 ` Jan Vrany
2019-03-05 20:53 ` Pedro Alves
2019-03-06 15:09 ` Jan Vrany
2019-03-06 15:45 ` Eli Zaretskii [this message]
2019-03-06 16:37 ` Jan Vrany
2019-03-06 17:36 ` Eli Zaretskii
2019-03-11 8:46 ` Readline on Windows (WAS: Re: [PATCH v2 0/2] MI: Add new command -complete] Jan Vrany
2019-03-11 14:43 ` Eli Zaretskii
2019-03-12 11:43 ` Jan Vrany
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83k1hcc8hv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=jan.vrany@fit.cvut.cz \
--cc=palves@redhat.com \
--cc=tom@tromey.com \
/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).