This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Readline on Windows (WAS: Re: [PATCH v2 0/2] MI: Add new command -complete]


> From: Jan Vrany <jan.vrany@fit.cvut.cz>
> Cc: palves@redhat.com, tom@tromey.com, gdb@sourceware.org
> Date: Mon, 11 Mar 2019 08:45:55 +0000
> 
> Ah, sorry, I should have been more clear. I meant that it does not work
> for me EVEN when on standard console so I doubted it would work better over 
> pipes much better.
> 
> All the problems I described do happen when using standard console and never
> worked no matter which GDB I used (compiled by myself or by some third party).

That's strange.  Do you have some curses library installed, and if so,
does it get linked into GDB?

> > Do you perhaps have a ~/.inputrc file, or some other local
> > customization, which might affect how Readline works? 
> 
> Not that I know of. There's no ".inputrc" nor "inputrc" on my Windows filesystem.
> I believe GDB compiled by myself uses the readline that comes with GDB.

The .inputrc file doesn't come with Readline, it is a user init file
that you yourself can create to customize how input through readline
works.

I compile GDB myself as well, also with its bundled readline, I use
GDB in the Windows console all the time, and I have no problems like
the ones you describe.  Very strange.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]