public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Ofir Cohen <ofircohenn@gmail.com>
To: gdb@sourceware.org
Subject: building gdb with TUI support on Windows
Date: Fri, 26 Dec 2014 00:13:00 -0000	[thread overview]
Message-ID: <CAHOBVAer1jbry4Ksxwj0D5dYC_d7c60vqoeh69Fry8L+zErSzA@mail.gmail.com> (raw)

Hi guys,
I'm trying to build gdb from source with TUI support on Windows.
I'm using msys2 with MinGWx64.
It seems non-trivial, and is accompanied by undesired behavior.

I'm addressing this mailing list after a long period of trying by myself
and because I couldn't find a decent place where this could be solved.

I manage to build by commenting out tputs() implementation in
gdb/windows-termcap.c
(so the ncurses tputs is used instead).

However,
when I run: "gdb --tui"
from msys2 I get a "TUI mode not supported".

When I run it from DOS (with mingw64 paths in the PATH), it runs but I
cannot move the text

cursor to left arrow and right arrow), and even more annoying, I can't
use the CTRL+R

(history lookup).

I saw some post about gdb with TUI support on Windows:
http://migeel.sk/blog/2009/04/15/compiling-gdb-under-windows/

But it didn't help.

Do you have any idea how to get it done right?

P.S. this is how I build
export FLAGS="--enable-tui=no --with-expat --disable-gdbserver
--with-sysroot=\"remote:\" --build=x86_64-w64-mingw32"
./configure $FLAGS
make -j 8

Your help is very much appreciated =].

Thanks,
Ofir Cohen

             reply	other threads:[~2014-12-26  0:13 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26  0:13 Ofir Cohen [this message]
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
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=CAHOBVAer1jbry4Ksxwj0D5dYC_d7c60vqoeh69Fry8L+zErSzA@mail.gmail.com \
    --to=ofircohenn@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).