improve
security, as gcc 3 used to.
On 1/25/07, Denis Vlasenko <[EMAIL PROTECTED]> wrote:
On Thursday 25 January 2007 01:43, In Cognito wrote:
> > > 0x080483a7 :sub$0x208,%esp
> > > 0x080483ad :mov0x8(%ebp),%eax
> > > 0x080483b0 : mov%eax,0x
onger there.
On 1/24/07, Denis Vlasenko <[EMAIL PROTECTED]> wrote:
On Thursday 25 January 2007 01:22, In Cognito wrote:
> Hello,
>
> It's nice to see a more security-minded release of gcc with v4.
> Variables are moved around to reduce chances for exploitation,
> -fstack-pro
Hello,
It's nice to see a more security-minded release of gcc with v4.
Variables are moved around to reduce chances for exploitation,
-fstack-protector, etc. Great!
Why are local variables once-again adjacent to the saved frame pointer
though? gcc v 2 called and wants one of its "features" back.
