From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-developers@cygwin.com
Cc: JonY <10walls@gmail.com>
Subject: Re: Cyg32 on Win64 fails with stack-protector
Date: Fri, 01 Jun 2018 10:06:00 -0000 [thread overview]
Message-ID: <20180601100644.GA6322@calimero.vinschen.de> (raw)
In-Reply-To: <1eafb042-ec51-cf01-78f3-445db62dd015@cornell.edu>
[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]
On May 31 09:13, Ken Brown wrote:
> On 5/31/2018 4:18 AM, Corinna Vinschen wrote:
> > On May 30 19:29, Bill Zissimopoulos wrote:
> > > Corinna, thanks for your response.
> > >
> > > On 5/29/18, 9:59 AM, Corinna Vinschen wrote:
> > >
> > > > Hi Ben,
> > > >
> > > > On Apr 27 19:12, Ben RUBSON wrote:
> > > > > Hi,
> > > > >
> > > > > We are facing an issue with Cygwin 2.10 32 bits running on Windows 64
> > > > > bits.
> > > > >
> > > > > Issue was found running EncFS FUSE FS using WinFsp.
> > > > >
> > > > > When forking, and calling StartServiceCtrlDispatcher, program fails with
> > > > > 0xC0000028 / STATUS_BAD_STACK.
> > > > >
> > > > > Testing several Cygwin versions reveals that issue was introduced
> > > > > between
> > > > > 2017-11-14 and 2017-12-01.
> > > > > And Bill (WinFsp author) found that compiling with -fno-stack-protector
> > > > > works around the issue.
> > > > >
> > > > > There you can then find the full story and Bill's nice investigation :
> > > > > https://github.com/billziss-gh/winfsp/issues/161
> > > > >
> > > > > Could it be possible something went wrong with Cygwin ?
> > > > >
> > > > > Thank you very much for your support !
> > > >
> > > > Even with Bill's additionl info I have no idea what change in the
> > > > above time frame might be the culprit, especially since no change
> > > > has been made to stack handling.
> > > >
> > > > I suggest to build your own Cygwin and bisect it. Also, you
> > > > may want to run your stuff under GDB and set breakpoints to, e.g.,
> > > > Cygwin's exception::handle method. Make sure the cygwin1.dbg
> > > > file can be found by GDB.
> > >
> > > There appear to be some SSP related commits in the discussed time frame.
> > > For example:
> > >
> > > https://sourceware.org/git/?p=newlib-cygwin.git;a=commitdiff;h=0a5dfdbd1ba3
> > > 663a54fa1a7de1a6c4a0a3316a6e
> > >
> > > Another possibility would be a change in the gcc default options between
> > > Cygwin 2.9 and Cygwin 2.10. I do not know if this is possible, but perhaps
> > > gcc in 2.9 compiles with -fstack-protector disabled by default and gcc in
> > > 2.10 compiles with it enabled by default?
> > >
> > > Bill
> >
> > I CCed Ken (gcc) and Yaakov (SSP) to get more qualified input than
> > my own Cygwin DLL centric view.
>
> I think you meant to CC a different Ken.
Oops, I meant to CC a JonY, in fact, not a Ken at all. Sorry!
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-06-01 10:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 17:12 Ben RUBSON
2018-05-29 17:01 ` Corinna Vinschen
2018-05-30 19:29 ` Bill Zissimopoulos
2018-05-31 8:19 ` Corinna Vinschen
2018-05-31 13:13 ` Ken Brown
2018-06-01 10:06 ` Corinna Vinschen [this message]
2018-06-01 10:50 ` JonY
2018-06-20 16:42 ` Ben RUBSON
2018-06-21 9:43 ` JonY
2018-06-20 16:50 ` Ben RUBSON
2018-06-20 17:21 ` Ford, Brian
2018-06-21 7:21 ` Corinna Vinschen
2018-06-23 13:50 ` Ben RUBSON
2018-06-25 9:44 ` Corinna Vinschen
2018-06-25 15:36 ` Carter, Mark Andrew (Andy)
2018-06-25 16:08 ` Ben RUBSON
2018-04-27 20:29 Bill Zissimopoulos
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=20180601100644.GA6322@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=10walls@gmail.com \
--cc=cygwin-developers@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).