Re: Executing from dynamically allocated memory

chakaram@auth.gr
Sat, 12 Oct 2013 19:20:45 +0300

          From comp.compilers
Related articles
Executing from dynamically allocated memory news@fx32.iad.highwinds-media.com (news) (2013-10-12)
Re: Executing from dynamically allocated memory james.harris.1@gmail.com (James Harris) (2013-10-12)
Re: Executing from dynamically allocated memory sebastien.fricker@gmail.com (=?UTF-8?B?U8OpYmFzdGllbiBGcmlja2Vy?=) (2013-10-12)
Re: Executing from dynamically allocated memory chakaram@auth.gr (2013-10-12)
Re: Executing from dynamically allocated memory blog@rivadpm.com (Alex McDonald) (2013-10-12)
Re: Executing from dynamically allocated memory sandmann@cs.au.dk (2013-10-12)
Re: Executing from dynamically allocated memory jkallup@web.de (Jens Kallup) (2013-10-13)
| List of all articles for this month |
From: chakaram@auth.gr
Newsgroups: comp.compilers
Date: Sat, 12 Oct 2013 19:20:45 +0300
Organization: Compilers Central
References: 13-10-004
Keywords: architecture, code
Posted-Date: 12 Oct 2013 14:53:53 EDT

As our moderator pointed out, sounds like NX. Use mmap() with
PROT_READ|PROT_WRITE|PROT_EXEC or just PROT_WRITE and then mprotect()
your region to PROT_READ|PROT_EXEC.


If you're on an i386, then it's probably some kernel hardening patch
that makes the heap non executable.
./ck
--
Chariton Karamitas
Electrical and Computer Engineering Department
Fuculty of Engineering
Aristotle University of Thessaloniki, Greece


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.