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: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
Date: Wed, 19 Jan 2022 18:39:11 +0900	[thread overview]
Message-ID: <20220119183911.3ef67396328c33cccd83a050@nifty.ne.jp> (raw)
In-Reply-To: <announce.05958013-de02-c5ee-e238-c2d89ea65665@dronecode.org.uk>

On Mon, 17 Jan 2022 18:57:26 +0000
Jon Turney wrote:
> * Use cygwin pgid if inferior is a cygwin process (Takashi Yano)
>    Addresses: https://cygwin.com/pipermail/cygwin/2021-January/247640.html

I confirmed that the followigin problem is fixed in this TEST
version.

> 1) Install coreutils-debuginfo package.
> 2) Run "gdb cat" in console (command prompt), not in mintty.
> 3) Enter "start" in gdb.
> 4) Enter "cont" in gdb.
> 
> This results in:
> /usr/bin/cat: -: Input/output error

Thanks.


However, I noticed another problem in signal handling.

Even with the following setting (by default),
(gdb) info signal SIGINT
Signal        Stop      Print   Pass to program Description
SIGINT        Yes       Yes     No              Interrupt

inferior receives SIGINT when Ctrl-C is pressed.
Due to this behaviour, inferior cannot be continued
by 'cont' command after Ctrl-C. Is this the known issue?

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

  reply	other threads:[~2022-01-19  9:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-17 18:57 Jon Turney
2022-01-19  9:39 ` Takashi Yano [this message]
2022-01-24 14:46   ` Jon Turney
2022-01-24 15:01     ` Takashi Yano
2022-04-18 16:09       ` Takashi Yano
2022-05-16 16:35         ` Takashi Yano
2022-05-18 12:21           ` Jon Turney

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=20220119183911.3ef67396328c33cccd83a050@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).