Re: [ANNOUNCEMENT] gdb 11.2-1 (TEST)

[Takashi Yano <takashi.yano@nifty.ne.jp>]

On Tue, 19 Apr 2022 01:09:52 +0900
Takashi Yano wrote:
> On Tue, 25 Jan 2022 00:01:53 +0900
> Takashi Yano wrote:
> > On Mon, 24 Jan 2022 14:46:20 +0000
> > Jon Turney wrote:
> > > On 19/01/2022 09:39, Takashi Yano wrote:
> > > > 
> > > > 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?
> > > 
> > > Not known by me.
> > > 
> > > Are you saying this is a new issue in this gdb package?
> > 
> > Probably, this is not a new issue. But, it was hidden by:
> > > * Use cygwin pgid if inferior is a cygwin process (Takashi Yano)
> > >    Addresses: https://cygwin.com/pipermail/cygwin/2021-January/247640.html
> 
> This problem was solved in cygwin1.dll side by adding
> workaround for GDB.
> https://cygwin.com/pipermail/cygwin-patches/2022q1/011778.html
> https://cygwin.com/pipermail/cygwin-patches/2022q2/011876.html
> etc.
> 
> The workaraound will be available in upcomming cygwin 3.3.5.

Is there any plan to release gdb 11.2-1 ?
Now gdb 11.2-1(TEST) works fine for me with cygwin 3.3.5.

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