Hi Bart
Bart Veer wrote:
> Basically -fstack-protector depends on some extra work done by the
> glibc startup code. Of course the synthetic target does not use glibc
> so that extra bit of initialization does not happen. The extra init is
> not straightforward. It involves manipulating the x86 se
> "John" == John Dallaway writes:
John> Hi Rutger
John> Rutger Hofman wrote:
>> An aside: I run Ubuntu. At first, I couldn't run synth at all.
>> Applications would crash, and gdb would crash on the
>> application too! After some list searching, I found out that
>> th
> Do you understand _why_ eCos is crashing with the GCC stack protector
> enabled? Is it due to an assumption made in eCos regarding the stack
> frame which could be corrected? We should ensure we understand the
> nature of the failure before disabling this feature.
Bart looked at this a while bac
Hi Rutger
Rutger Hofman wrote:
> An aside: I run Ubuntu. At first, I couldn't run synth at all.
> Applications would crash, and gdb would crash on the application too!
> After some list searching, I found out that this probably is
> Ubuntu-specific. We need to include -fno-stack-protector in the
