From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Emacs-w32... Still Crashing
Date: Wed, 09 Jul 2014 10:27:00 -0000 [thread overview]
Message-ID: <20140709102705.GF26447@calimero.vinschen.de> (raw)
In-Reply-To: <20140708164418.GA4963@ednor.casa.cgf.cx>
[-- Attachment #1: Type: text/plain, Size: 1902 bytes --]
On Jul 8 12:44, Christopher Faylor wrote:
> On Tue, Jul 08, 2014 at 11:36:07AM -0500, Yaakov Selkowitz wrote:
> >On 2014-07-08 10:02, Christopher Faylor wrote:
> >> On Tue, Jul 08, 2014 at 09:55:55AM -0400, Ken Brown wrote:
> >>> Grasping at straws, as usual, I wonder if these mysterious crashes could
> >>> be related to a bug that Corinna just fixed:
> >>>
> >>> https://cygwin.com/ml/cygwin-cvs/2014-q3/msg00004.html
> >>>
> >>> Corinna, is this plausible? If so, maybe Gustav should try the next
> >>> snapshot of the Cygwin DLL. (The current one doesn't seem to have this
> >>> fix in it.)
> >>
> >> Actually, I was scratching my head over that change and wondering
> >> what it was supposed to solve.
> >
> >We believe that this was the cause of e.g. mandb aborting on x86_64
> >without manually enlarging the stack commit size:
>
> "We"?
Yaakov and me in a discussion with integrated testing on IRC. What are
you trying to imply?
> Isn't that testable by setting the stack size down and putting a
> printf in cygwin somewhere?
>
> In any event, the comment in my code which is supposed to explain why
> the tag is commented out is lacking details. If this patch is a joint
> effort then please add more details to the change that you made to my
> code.
It's not your code. The function exception::myfault_handle has been
written by me to workaround the lack of structured exception handling in
GCC on x86_64.
I don't understand what's unclear in this comment. exception::myfault_handle
is a vectored exception handler (see the comment preceeding the method)
so it short-circuits structured exception handling. Thus it short-circuits
PAGE_GUARD handling, aka stack commits.
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:[~2014-07-09 10:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 19:15 Zdzislaw Meglicki
2014-07-08 13:56 ` Ken Brown
2014-07-08 15:02 ` Christopher Faylor
2014-07-08 16:36 ` Yaakov Selkowitz
2014-07-08 16:44 ` Christopher Faylor
2014-07-09 10:27 ` Corinna Vinschen [this message]
2014-07-09 10:42 ` Corinna Vinschen
2014-07-09 10:15 ` Corinna Vinschen
2014-07-09 12:22 ` Corinna Vinschen
2014-07-09 13:52 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2014-06-17 14:28 Emacs-w32... still crashing Zdzislaw Meglicki
2014-06-04 14:24 Zdzislaw Meglicki
2014-06-03 22:03 Zdzislaw Meglicki
2014-06-05 19:05 ` Ken Brown
2014-06-05 19:51 ` Christopher Faylor
2014-06-05 20:09 ` Ken Brown
2014-06-06 7:53 ` Csaba Raduly
2014-06-03 20:04 Zdzislaw Meglicki
2014-06-03 21:37 ` Larry Hall (Cygwin)
2014-06-04 12:46 ` Ken Brown
2014-06-03 18:00 Zdzislaw Meglicki
2014-05-21 22:55 Zdzislaw Meglicki
2014-05-22 1:11 ` Ken Brown
2014-05-19 14:42 Zdzislaw Meglicki
2014-05-19 21:13 ` Ken Brown
2014-05-21 19:14 ` Ken Brown
2014-05-14 22:31 Zdzislaw Meglicki
2014-05-15 0:07 ` 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=20140709102705.GF26447@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).