This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Cyg32 on Win64 fails with stack-protector
- From: Ben RUBSON <ben dot rubson at gmail dot com>
- To: JonY <10walls at gmail dot com>, cygwin-developers at cygwin dot com
- Date: Wed, 20 Jun 2018 18:42:32 +0200
- Subject: Re: Cyg32 on Win64 fails with stack-protector
- References: <8A9D918F-F233-48DA-9B98-B87D7B188C21@gmail.com> <20180529165958.GK3501@calimero.vinschen.de> <D7344877.12258%billziss@navimatics.com> <20180531081835.GA14289@calimero.vinschen.de> <1eafb042-ec51-cf01-78f3-445db62dd015@cornell.edu> <20180601100644.GA6322@calimero.vinschen.de> <d7df0539-222c-b919-5e51-0b036f6ceb7b@gmail.com>
Bill, Corinna, Jony, thank you very much for your answers and details on
this topic.
And sorry for my late answer, I was totally stuck on some critical subjects
last days...
On 01 Jun 2018 12:49, JonY wrote:
On 06/01/2018 10:06 AM, Corinna Vinschen wrote:
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?
libssp in gcc was disabled in favor of newlib's, not sure if that has
something to do with it too.
Jony, do you mean that compilation options have changed, which could lead
to our issue ?
Would you manage to find out which change provided this ?
By any chance, between 2017-11-14 and 2017-12-01 ?
Thank you again,
Best regards,
Ben