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: dynamically written code problem

From: Paolo Bonzini <bonzini at gnu dot org>
To: Tolga Dalman <ates100 at web dot de>
Cc: GCC Development <gcc at gcc dot gnu dot org>
Date: Thu, 14 Oct 2004 13:45:25 +0200
Subject: Re: dynamically written code problem
References: <002801c4af13$83537260$6401a8c0@bwdesk> <416A3480.5020409@gnu.org> <20041011072528.GL30497@sunsite.ms.mff.cuni.cz> <416A3881.6080507@polimi.it> <20041011074454.GB31909@devserv.devel.redhat.com> <416A4003.4010700@polimi.it> <20041014130429.7acd7351.ates100@web.de>

the mprotect man-page says:
" POSIX.1b says  that  mprotect  can  be  used  only on regions of memory
obtained from mmap(2)."
is there a way to set the PROT_EXEC flag on arbitrary malloc'ed space ? at least, using mprotect is (currently) not POSIX conforming.

That code was explicitly for Linux, where there is no difference (at least in this respect) between sbrk- and mmap-allocated VMAs (virtual memory areas).

Paolo

References:
- dynamically written code problem
  - From: Bob Wilkinson
- Re: dynamically written code problem
  - From: Paolo Bonzini
- Re: dynamically written code problem
  - From: Jakub Jelinek
- Re: dynamically written code problem
  - From: Paolo Bonzini
- Re: dynamically written code problem
  - From: Jakub Jelinek
- Re: dynamically written code problem
  - From: Paolo Bonzini
- Re: dynamically written code problem
  - From: Tolga Dalman

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