public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Takashi Yano <takashi.yano@nifty.ne.jp>
Cc: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST: Cygwin 3.1.0-0.1
Date: Tue, 13 Aug 2019 10:48:00 -0000	[thread overview]
Message-ID: <20190813104753.GU11632@calimero.vinschen.de> (raw)
In-Reply-To: <20190812153613.GN11632@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

On Aug 12 17:36, Corinna Vinschen wrote:
> On Aug 12 22:44, Takashi Yano wrote:
> > [...]
> > (4) Segmentation fault occurs in some cases regarding signalfd.
> > [...]
> > However, I can not find out the cause of problem (4). This seems
> > to affect only 32bit version of cygwin.
> > 
> > To reproduce (4), use a simple test case attached (signalfd-chk.c).
> > Compile it and execute, then type 'q' or '^C' to stop it.
> > This causes segmentation fault.
> > 
> > I am not sure why, but, the patch attached (signalfd-segfault.diff)
> > resolves the problem (4).
> > 
> > Could you please have a look?
> 
> Will do.  The place where it supposedly crashes looks weird.  But
> I don't see how your patch should be the right thing to do.

I created a patch which *seems* to do the right thing.  I'm not
yet sure it's the best solution, but it seems to do the trick, at
least.

I'm just creating new developer snapshots, please try.  I'll
create another test release later this week.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-08-13 10:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 18:55 Corinna Vinschen
2019-08-11  7:28 ` Thorsten Kampe
2019-08-12 13:01   ` Corinna Vinschen
2019-08-12 19:44     ` Takashi Yano
2019-08-13 22:27       ` Thorsten Kampe
2019-08-13 21:45     ` Thorsten Kampe
2019-08-13 21:51       ` Thorsten Kampe
2019-08-14  7:23         ` Takashi Yano
2019-08-12 13:44 ` Takashi Yano
2019-08-12 15:36   ` Corinna Vinschen
2019-08-13 10:48     ` Corinna Vinschen [this message]
2019-08-14 11:41       ` Takashi Yano
2019-08-14 11:47         ` Takashi Yano
2019-08-14 13:49           ` Corinna Vinschen
2019-08-14 19:21             ` Takashi Yano
2019-08-15  7:49               ` Corinna Vinschen
2019-08-15 10:36                 ` Corinna Vinschen
2019-08-15 15:04                   ` Corinna Vinschen
2019-08-15 15:09                     ` Corinna Vinschen
2019-08-16 14:58                       ` Corinna Vinschen
2019-08-17 16:59                         ` Takashi Yano
2019-08-18 12:07                           ` Corinna Vinschen
2019-08-18 12:08 ` Achim Gratz
2019-08-18 14:29   ` Corinna Vinschen
2019-08-18 14:51     ` Achim Gratz
2019-08-19  8:56       ` Corinna Vinschen

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=20190813104753.GU11632@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=takashi.yano@nifty.ne.jp \
    /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).