On 16/05/2025 22:37, Jon Turney via Cygwin wrote:
On 16/05/2025 16:43, Takashi Yano wrote:
Hi Jon,
[...]
I could reproduce that. And also found cygwin 3.4.10 does not have this
issue. I'll look into this.
I could bisect the issue and found the next commit triggered the issue.
commit 914573
On 16/05/2025 16:43, Takashi Yano wrote:
Hi Jon,
[...]
I could reproduce that. And also found cygwin 3.4.10 does not have this
issue. I'll look into this.
I could bisect the issue and found the next commit triggered the issue.
commit 91457377d6c9f89a08b1b70e45cbae87ef467119
Author: Jon Turn
Hi Jon,
On Fri, 16 May 2025 21:14:00 +0900
Takashi Yano via Cygwin wrote:
> On Fri, 16 May 2025 13:46:21 +0200
> Christian Franke wrote:
> > Testcase:
> >
> > $ uname -r # Also occurs with 3.6.1-1.x86_64
> > 3.7.0-0.95.g854150fda310.x86_64
> >
> > $ cat sigsegv.c
> > int main()
> > {
> > *(v
Hi Christian,
Thanks for the report.
On Fri, 16 May 2025 13:46:21 +0200
Christian Franke wrote:
> Found during check why SIGSEGV handler could interrupt SIGALRM handler
> (which does not happen on Linux):
> https://sourceware.org/pipermail/cygwin-patches/2025q2/013703.html
Perhaps, delay of cal
Found during check why SIGSEGV handler could interrupt SIGALRM handler
(which does not happen on Linux):
https://sourceware.org/pipermail/cygwin-patches/2025q2/013703.html
Testcase:
$ uname -r # Also occurs with 3.6.1-1.x86_64
3.7.0-0.95.g854150fda310.x86_64
$ cat sigsegv.c
int main()
{
*(vo
5 matches
Mail list logo