From: Daniel Colascione <dancol@dancol.org>
To: cygwin@cygwin.com
Subject: Re: Please test snapshots
Date: Thu, 09 Aug 2012 06:35:00 -0000 [thread overview]
Message-ID: <5022F09C.6060501@dancol.org> (raw)
In-Reply-To: <20120808215909.GA29761@ednor.casa.cgf.cx>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On 8/8/2012 2:59 PM, Christopher Faylor wrote:
> On Mon, Aug 06, 2012 at 05:15:10PM -0700, Daniel Colascione wrote:
>> On 8/6/2012 2:07 PM, Daniel Colascione wrote:
>>> I just saw a hang building Emacs (using "make bootstrap")
>>
>> Signal handling appears to be broken. Here's a simple testcase. Run the program
>> and hit control-c. It'll print "got Alarm clock", then stop accepting any
>> signals at all, even SIGSTOP. The same program works fine on my Debian stable box.
>
> I forgot to send out a notice about this.
>
> This particular issue should be fixed in the latest snapshot.
The latest snapshot seems to fix the issue.
>
> You mention generic "signal handling" rather than "sigwaitinfo" so I don't
> know if there are other issues. It doesn't seem like much would work if
> signal handling was completely broken, though.
Apologies --- I should have been more specific. No, I haven't noticed any other
signal breakage aside from the sigwaitinfo problem and the Emacs build hang. I
can't reproduce either with the new snapshot.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-08-08 23:04 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 3:53 Christopher Faylor
2012-08-06 5:14 ` Daniel Colascione
2012-08-06 8:59 ` Achim Gratz
2012-08-08 13:04 ` Achim Gratz
2012-08-09 8:07 ` Achim Gratz
2012-08-06 15:31 ` Filipp Gunbin
2012-08-06 23:27 ` Daniel Colascione
2012-08-07 0:39 ` Daniel Colascione
2012-08-07 0:40 ` Daniel Colascione
2012-08-08 22:17 ` Christopher Faylor
2012-08-09 6:35 ` Daniel Colascione [this message]
2012-08-09 12:29 ` Achim Gratz
2012-08-09 14:54 ` Christopher Faylor
2012-08-09 15:06 ` Achim Gratz
2012-08-09 14:59 ` Daniel Colascione
2012-08-10 7:15 ` Achim Gratz
2012-08-10 14:36 ` Christopher Faylor
2012-08-10 18:12 ` Achim Gratz
2012-08-10 18:34 ` Christopher Faylor
2012-08-10 19:08 ` Achim Gratz
2012-08-10 20:24 ` Christopher Faylor
2012-08-10 20:37 ` Achim Gratz
2012-08-10 23:31 ` Christopher Faylor
2012-08-14 13:45 ` Adam Dinwoodie
2012-08-16 19:01 ` Christopher Faylor
2012-08-16 19:33 ` Ken Brown
2012-08-16 19:45 ` Christopher Faylor
2012-08-16 20:11 ` Ken Brown
2012-08-17 9:38 ` Adam Dinwoodie
2012-08-17 14:37 ` Christopher Faylor
2012-08-17 17:46 ` Adam Dinwoodie
2012-08-17 18:08 ` Christopher Faylor
2012-08-17 19:32 ` Achim Gratz
2012-08-17 9:40 ` Achim Gratz
2012-08-17 10:47 ` Achim Gratz
2012-08-14 19:23 ` jojelino
2012-08-14 19:41 ` Corinna Vinschen
2012-08-14 19:42 ` Christopher Faylor
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=5022F09C.6060501@dancol.org \
--to=dancol@dancol.org \
--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).