This is the mail archive of the
mailing list for the GCC project.
Re: gcc 3.4 nukes __guard
- From: Jim Wilson <wilson at specifixinc dot com>
- To: Travis Tilley <ttilley at email dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 19 May 2004 16:10:07 -0700
- Subject: Re: gcc 3.4 nukes __guard
- References: <20040517090920.69AC83740C4@ws3-2.us4.outblaze.com>
Travis Tilley wrote:
i have stack smashing protection patched into glibc, and all binaries compiled with stack protector need it:
gcc 3.4 nukes these symbols entirely. when i marked __guard and __guard_setup as __attribute__((used)), they became local instead of global... what am i doing wrong here?
There isn't enough info here to answer this. We need enough info to
reproduce the problem, preferably a small testcase. It is too much to
ask us to compile a patched glibc to try to reproduce a problem.
How is the __guard variable defined? How does the __guard variable get
into the application? Don't you also need a gcc patch for this? Maybe
the gcc patch has a bug?
Maybe you can ask the authors of the stack-smashing protection patch for
a version of the patch that works with gcc-3.4.
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com