This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: libffi on OpenBSD x86

From: Thomas Heller <theller at python dot net>
To: Andrew Haley <aph at redhat dot com>
Cc: Anthony Green <green at redhat dot com>,libffi-discuss at sources dot redhat dot com, gcc at gcc dot gnu dot org
Date: Wed, 20 Oct 2004 15:53:20 +0200
Subject: Re: libffi on OpenBSD x86
References: <mzyhpmsg.fsf@python.net><1098279488.3042.8.camel@localhost.localdomain><16758.27597.931165.96685@cuddles.cambridge.redhat.com>

Andrew Haley <aph@redhat.com> writes:

> Anthony Green writes:
>  > On Wed, 2004-10-20 at 06:00, Thomas Heller wrote:
>  > > but it seems the stack smashing protection that OpenBSD uses prevents
>  > > ffi_call from working correctly.
>  > > I found the -fno-stack-protector command line option for gcc, and
>  > > specifying this did the trick.
>  > > 
>  > > Now I'm not sure if there is a pragma which allows to disable the stack
>  > > protector from within the C source file, or should it be added to
>  > > libffi/configure somehow, or is there a way to pass this switch when
>  > > running libffi/configure?
>  > 
>  > IIRC, this flag comes from a set of third-party GCC patches.  It would
>  > certainly be easiest for the maintainer of those patches to cover the
>  > libffi directory as well.
>
> I'd like to know how this stack protector works.  Does it change the ABI?

What I found was this - it may or may not answer your question:

http://www.trl.ibm.com/projects/security/ssp/

Thomas

References:
- libffi on OpenBSD x86
  - From: Thomas Heller
- Re: libffi on OpenBSD x86
  - From: Anthony Green
- Re: libffi on OpenBSD x86
  - From: Andrew Haley

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]