From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: building gdb with TUI support on Windows
Date: Mon, 29 Dec 2014 00:41:00 -0000 [thread overview]
Message-ID: <1776056521.2146797.1419813685734.JavaMail.yahoo@jws11121.mail.ir2.yahoo.com> (raw)
In-Reply-To: <CAHOBVAdHx7XU+q8DXEWsY90HhKraUC+ajbtO1mLo_cg1H_gymQ@mail.gmail.com>
Ofir Cohen <ofircohenn@gmail.com> schrieb am 0:34 Montag, 29.Dezember 2014:
> Hi Hannes,
> I followed your advice, but I get compilation errors.
>
> 1) build pdcurses (with patched tputs)
> a. copy term.h/curses.h to /mingw64/include and /mingw64/include/ncurses
> b. copy libncurses.a to /mingw64/lib/
> 1) cd gdb-7.8
> 2) mkdir build; cd build
> 3) .././configure --enable-tui --with-expat --build=x86_64-w64-mingw32
> 4) make
> 5) from DOS:
> a) set PATH=c:\msys64\mingw64\bin\;%PATH%
> b) d:\gdb-7.8\build\gdb\gdb --tui
>
> and even tried more to force use the ncurses termcap with:
> .././configure --enable-tui --with-curses --with-expat
> --build=x86_64-w64-mingw32
>
> But on TUI mode, the left/right/up arrows still don't work.
> Neither does the CTRL+R (history lookup).
So you had some compilation errors which you fixed yourself?
> Though when you quit TUI mode (CTRL +x, a), the arrows start functioning,
> and then when you go back to TUI mode (same keys combination), they don't work.
>
> Do the arrow keys work for you when you're in TUI mode?
> What do you think is the problem?
>
> Note: the samples that come with pdcurses work, and the arrow keys
> function there.
> So it seems to be a gdb per se problem, and not some lack of support
> from the library.
I just retried CTRL+R and the arrow keys in TUI and normal mode, all works.
You are aware that with the arrow keys in TUI mode you move in the source
window, and not in the history?
But I can't explain why CTRL+R doesn't work for you.
Does it work in normal mode?
My build uses libiconv as well (to display unicode strings), but I don't think
this makes any difference for this case.
next prev parent reply other threads:[~2014-12-29 0:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 0:13 Ofir Cohen
2014-12-26 8:04 ` Eli Zaretskii
2014-12-27 13:53 ` Ofir Cohen
[not found] ` <CAHOBVAdux2M9aRnkJh1hDm_9VCTD6kVzWkF2fjj84qy8UJuh7w@mail.gmail.com>
2014-12-27 14:13 ` Eli Zaretskii
2014-12-27 14:40 ` Hannes Domani
2014-12-27 18:32 ` Eli Zaretskii
2014-12-28 13:58 ` Hannes Domani
2014-12-28 16:41 ` Ofir Cohen
2014-12-28 17:09 ` Hannes Domani
2014-12-28 23:34 ` Ofir Cohen
2014-12-29 0:41 ` Hannes Domani [this message]
2014-12-29 15:28 ` Ofir Cohen
[not found] ` <946370725.2390231.1419869855237.JavaMail.yahoo@jws11110.mail.ir2.yahoo.com>
2014-12-29 16:20 ` Hannes Domani
2014-12-30 19:15 ` Hannes Domani
2014-12-30 20:10 ` Ofir Cohen
2014-12-30 20:39 ` Hannes Domani
2014-12-31 16:34 ` Eli Zaretskii
2015-01-01 12:28 ` Hannes Domani
2015-01-01 15:42 ` Eli Zaretskii
2014-12-31 21:12 ` Ofir Cohen
2015-01-01 14:26 ` Hannes Domani
2015-01-01 15:14 ` Ofir Cohen
2015-01-01 15:47 ` Eli Zaretskii
2015-01-01 16:33 ` Ofir Cohen
2015-01-01 16:42 ` Eli Zaretskii
2015-01-01 16:48 ` Joel Sherrill
2015-01-01 17:18 ` Eli Zaretskii
[not found] ` <CAHOBVAcF824319G6O_LfJBYAQP3M0-LbhAV_d=SrR6jM4=0k5w@mail.gmail.com>
[not found] ` <83d26ybcap.fsf@gnu.org>
2015-01-02 0:32 ` Ofir Cohen
2014-12-28 18:38 ` Sergio Durigan Junior
2014-12-29 2:43 ` Joel Brobecker
2014-12-29 3:15 ` Joel Sherrill
2014-12-29 3:21 ` Joel Brobecker
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=1776056521.2146797.1419813685734.JavaMail.yahoo@jws11121.mail.ir2.yahoo.com \
--to=ssbssa@yahoo.de \
--cc=gdb@sourceware.org \
/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