public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: cgdb terminal handling problems
Date: Thu, 23 Jan 2020 12:52:00 -0000	[thread overview]
Message-ID: <20200123215247.62442b296b7ed384c94f2fb2@nifty.ne.jp> (raw)
In-Reply-To: <20200118131140.e570f34a4f9a9d63b7e58d37@nifty.ne.jp>

On Sat, 18 Jan 2020 13:11:40 +0900
Takashi Yano wrote:
> On Fri, 17 Jan 2020 16:40:03 +0000 (GMT Standard Time)
> Arthur Norman wrote:
> > [80X[80C[?25h[?25lbreakpoints-invalid[?25h[?25l
> > [80X[80C[?25h[?25l[80X[80C[?25h[?25l
> > Breakpoint 1,[67X[67C[?25h[?25l[80X[80C[?25h[?25lmain[76X[76C[?25h[?25l ([78X[78
> > C[?25h[?25largc[76X[76C[?25h[?25l=[79X[79C[?25h[?25l1[79X[79C[?25h[?25l,[79X[79C
> > [?25h[?25largv[76X[76C[?25h[?25l=[79X[79C[?25h[?25l
> > [80X[80C[?25h[?25larg-value *[?25h[?25l
> > 0xffffcc40[70X[70C[?25h[?25l)[79X[79C[?25h[?25l at[77X[77C[?25h[?25lhello.cpp[71
> > X[71C[?25h[?25l:[79X[79C[?25h[?25l5[79X[79C[?25h[?25l[80X[80C[?25h[?25l[?25h[?25
> > l
> > [80X[80C[?25h[?25l[80X[80C[?25h[?25l[80X[80C[?25h[?25l[80X[80C[?25h[?25l(gdb)[75
> > X[75C[?25h[?25l
> 
> This is obviously a pseudo console related issue.
> Please give me time.

I propose a patch which able to disable the pseudo console featre
in pty, and it was accepted. With this patch, cgdb can work as
before by:

env CYGWIN=disable_pcon cgdb progname

You can also use alias

alias cgdb="env CYGWIN=disable_pcon cgdb"

Please wait for new cygwin release.

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2020-01-23 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 16:40 Arthur Norman
2020-01-18  4:11 ` Takashi Yano
2020-01-23 12:52   ` Takashi Yano [this message]

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=20200123215247.62442b296b7ed384c94f2fb2@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin@cygwin.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).