On Thu, Sep 24, 2009 at 03:32:43AM -0000, Alan Modra wrote:
> Huh. You have what looks like ppc64 code in there.
>
> 4c: 80 02 8f f8 lwz r0,-28680(r2)
> 50: 90 01 00 3c stw r0,60(r1)
>
> Where did that come from? It seems you have _FORTIFY_SOURCE defined for
> you too, somehow. Maybe that is pulling in a bad printf define? Please
> attach the .i generated by "gcc -E -fPIE -Os test.c"
-D_FORTIFY_SOURCE=2 is a default in Ubuntu's compiler. It can be turned
off with -U_FORTIFY_SOURCE in the build if you want to see if that could be
causing the glitch.
On Thu, Sep 24, 2009 at 03:32:43AM -0000, Alan Modra wrote:
> Huh. You have what looks like ppc64 code in there.
>
> 4c: 80 02 8f f8 lwz r0,-28680(r2)
> 50: 90 01 00 3c stw r0,60(r1)
>
> Where did that come from? It seems you have _FORTIFY_SOURCE defined for
> you too, somehow. Maybe that is pulling in a bad printf define? Please
> attach the .i generated by "gcc -E -fPIE -Os test.c"
-D_FORTIFY_SOURCE=2 is a default in Ubuntu's compiler. It can be turned
off with -U_FORTIFY_SOURCE in the build if you want to see if that could be
causing the glitch.
https:/ /wiki.ubuntu. com/CompilerFla gs
--
Kees Cook
Ubuntu Security Team