Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Hannes Domani <ssbssa@yahoo.de>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: building gdb with TUI support on Windows
Date: Sun, 28 Dec 2014 13:58:00 -0000	[thread overview]
Message-ID: <1716575811.1998535.1419775088162.JavaMail.yahoo@jws11115.mail.ir2.yahoo.com> (raw)
In-Reply-To: <83h9whkkph.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> schrieb am 19:32 Samstag, 27.Dezember 2014:
> > Date: Sat, 27 Dec 2014 14:39:46 +0000 (UTC)
> > From: Hannes Domani <ssbssa@yahoo.de>
> >
> > You might want to check out this link (plus the comments):
> > http://opensourcepack.blogspot.co.at/2012/02/gdb-74-with-tui-win32.html
> 
> Thank.  May I encourage you to report those problems with the patches?
> It would be nice to have them upstream (the latest version of GDB is
> 7.8.1, with 7.9 looming).

I forgot that I only had these problems with ncurses.
Since then I switched to pdcurses, it works much better (+faster) on windows.

I only had to change tputs() a bit.


  reply	other threads:[~2014-12-28 13:58 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 [this message]
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=1716575811.1998535.1419775088162.JavaMail.yahoo@jws11115.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