* [ANNOUNCEMENT] gdb 11.2-1 (TEST)
@ 2022-01-17 18:57 Jon Turney
2022-01-19 9:39 ` Takashi Yano
0 siblings, 1 reply; 7+ messages in thread
From: Jon Turney @ 2022-01-17 18:57 UTC (permalink / raw)
To: cygwin
The following package has been updated in the Cygwin distribution:
* gdb-11.2-1
The GNU debugger allows you to debug programs written in C, C++, and
other languages, by executing them in a controlled fashion and printing
their data.
This is an update to the latest upstream version:
https://sourceware.org/pipermail/gdb-announce/2022/000130.html
See the /usr/share/doc/gdb/NEWS file for a list of user-visible changes.
In addition, it contains the following patches carried forward from the
previous Cygwin package:
* Teach the demangler to deal with '@'-decorated __stdcall functions
* (experimental) Teach gdb how to unwind frames for the Cygwin signal
delivery wrapper functions _sigbe and sigdelayed
* Fix a memory leak which would occur in the case when the result of
realpath() is greater than or equal to SO_NAME_MAX_PATH_SIZE (Corinna
Vinschen)
* Simplify and improve handling of inferior context after a Cygwin signal
and the following new patches:
* Use cygwin pgid if inferior is a cygwin process (Takashi Yano)
Addresses: https://cygwin.com/pipermail/cygwin/2021-January/247640.html
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
2022-01-17 18:57 [ANNOUNCEMENT] gdb 11.2-1 (TEST) Jon Turney
@ 2022-01-19 9:39 ` Takashi Yano
2022-01-24 14:46 ` Jon Turney
0 siblings, 1 reply; 7+ messages in thread
From: Takashi Yano @ 2022-01-19 9:39 UTC (permalink / raw)
To: cygwin
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>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
2022-01-19 9:39 ` Takashi Yano
@ 2022-01-24 14:46 ` Jon Turney
2022-01-24 15:01 ` Takashi Yano
0 siblings, 1 reply; 7+ messages in thread
From: Jon Turney @ 2022-01-24 14:46 UTC (permalink / raw)
To: Takashi Yano, The Cygwin Mailing List
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?
This is an intersection of two tricky areas (Ctrl-C handling and signal
handling), so misbehaviour is believable :).
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
2022-01-24 14:46 ` Jon Turney
@ 2022-01-24 15:01 ` Takashi Yano
2022-04-18 16:09 ` Takashi Yano
0 siblings, 1 reply; 7+ messages in thread
From: Takashi Yano @ 2022-01-24 15:01 UTC (permalink / raw)
To: cygwin
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
--
Takashi Yano <takashi.yano@nifty.ne.jp>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
2022-01-24 15:01 ` Takashi Yano
@ 2022-04-18 16:09 ` Takashi Yano
2022-05-16 16:35 ` Takashi Yano
0 siblings, 1 reply; 7+ messages in thread
From: Takashi Yano @ 2022-04-18 16:09 UTC (permalink / raw)
To: cygwin
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.
--
Takashi Yano <takashi.yano@nifty.ne.jp>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
2022-04-18 16:09 ` Takashi Yano
@ 2022-05-16 16:35 ` Takashi Yano
2022-05-18 12:21 ` Jon Turney
0 siblings, 1 reply; 7+ messages in thread
From: Takashi Yano @ 2022-05-16 16:35 UTC (permalink / raw)
To: cygwin
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>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [ANNOUNCEMENT] gdb 11.2-1 (TEST)
2022-05-16 16:35 ` Takashi Yano
@ 2022-05-18 12:21 ` Jon Turney
0 siblings, 0 replies; 7+ messages in thread
From: Jon Turney @ 2022-05-18 12:21 UTC (permalink / raw)
To: The Cygwin Mailing List
On 16/05/2022 17:35, Takashi Yano wrote:
> 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.
Yes, past time to do that since I just starting looking at packaging
gdb-12.1 :-)
This package has been promoted from test to current.
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2022-05-18 12:21 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-17 18:57 [ANNOUNCEMENT] gdb 11.2-1 (TEST) Jon Turney
2022-01-19 9:39 ` Takashi Yano
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
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).