From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated for 32-bit, new for 64-bit: libsigsegv-2.10-2
Date: Mon, 20 Jul 2015 19:02:00 -0000 [thread overview]
Message-ID: <20150720190235.GX3864@calimero.vinschen.de> (raw)
In-Reply-To: <55AD3B95.9050809@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1362 bytes --]
On Jul 20 12:19, Eric Blake wrote:
> On 07/18/2015 02:11 PM, Corinna Vinschen wrote:
>
> >> m4 was
> >> originally creating an alternate stack of 16k in size, based on a pure
> >> guess that it would be large enough (since the headers didn't declare
> >> any constant otherwise); but cygwin's sigaltstack() requires an
> >> alternate stack of 64k or larger.
> >
> > No, 32K (MINSIGSTKSZ) is sufficient.
> >
> >> I see a couple of options:
> >>
> >> 1. see if we can relax cygwin.dll to live with a 16k alternate stack
> >
>
> > So, what about MINSIGSTKSZ == 8192 and SIGSTKSZ == 32768?
> >
> > Or MINSIGSTKSZ == 16384 and SIGSTKSZ == 65536?
> >
> > That could go into Cygwin 2.2.0 which I could release next week.
>
> I just tested: m4-1.4.17-1 (which uses the 16k alt-stack, compared to
> 1.4.17-2 using 64k) coupled with the test cygwin 2.2.0-0.1 is once again
> able to make use of libsigsegv-2.10-2. And if I recompile m4 against
> cygwin 2.2.0-0.1 headers, I end up with a 32k stack which also works.
>
> That means that so far, I have not found any problems with your new
> smaller stack sizing requirements.
Thanks for testing. That's a good start.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-20 19:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <announce.55A98E29.4090001@redhat.com>
2015-07-18 18:18 ` Eric Blake
2015-07-18 20:11 ` Corinna Vinschen
2015-07-18 20:41 ` Eric Blake
2015-07-19 8:38 ` Corinna Vinschen
2015-07-20 11:20 ` Corinna Vinschen
2015-07-20 13:03 ` Ken Brown
2015-07-20 15:18 ` Corinna Vinschen
2015-07-21 20:06 ` Ken Brown
2015-07-21 20:25 ` Achim Gratz
2015-07-21 20:47 ` Ken Brown
2015-07-22 8:16 ` Corinna Vinschen
2015-07-22 12:10 ` Ken Brown
2015-07-22 16:22 ` Achim Gratz
2015-07-26 17:55 ` Achim Gratz
2015-07-26 21:09 ` Ken Brown
2015-07-20 18:19 ` Eric Blake
2015-07-20 19:02 ` Corinna Vinschen [this message]
2015-07-19 11:29 ` Ken Brown
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=20150720190235.GX3864@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-apps@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).