From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cgdb fails with cygwin 3.2.0 but is OK with 3.1.6
Date: Tue, 13 Apr 2021 12:55:55 -0500 [thread overview]
Message-ID: <85b3b94b-ccc2-b62a-acdd-156f019de651@gmail.com> (raw)
In-Reply-To: <alpine.WNT.2.00.2104131455150.56864@panamint>
On 4/13/2021 9:05 AM, Arthur Norman via Cygwin wrote:
> With the latest cygwin if I go "gcc -O0 -g hello.c -o hello" then "cgdb
> ./hello", break main, run then cgdb exits abruptly without sign on
> actually starting my code. If I use just gdb not cgdb all is OK. If I
> try "gcd -tui hello" I can single step my code but the display in the
> top half of the window is damaged - eg after a couple of steps it shows
> lines 5 and 6 of the source code twice each, but once normally and once
> in inverted video.
> Raw seems to gdb lets me step the code about as expected.
>
> If I revert just the cygwin package from 3.2.0-1 to 3.1.6-1 things
> appear to behave as I would expect. 3.1.7-1 possibly had -tui issues and
> led to cgdb stalling on my large and broken example code which is why I
> report 3.1.6-1 as the baseline.
At one time it was recommended to disable a Cygwin feature, something
like this:
alias cgdb="env CYGWIN=disable_pcon cgdb"
Not sure if this is still necesary.
--
R.Berber
next prev parent reply other threads:[~2021-04-13 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 14:05 Arthur Norman
2021-04-13 17:55 ` René Berber [this message]
2021-04-13 18:56 ` Arthur Norman
2021-04-13 19:13 ` René Berber
2021-04-14 3:20 ` Takashi Yano
2021-04-14 3:13 ` Takashi Yano
2021-04-14 7:28 ` Arthur Norman
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=85b3b94b-ccc2-b62a-acdd-156f019de651@gmail.com \
--to=rene.berber@gmail.com \
--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).