From: "\"Jørgen P. Tjernø\"" <jorgen@devsoft.no>
To: linux-c-programming@vger.kernel.org
Subject: Re: execve-type memory-based function, possible?
Date: Mon, 23 Oct 2006 12:20:12 +0200 [thread overview]
Message-ID: <453C975C.1010402@devsoft.no> (raw)
In-Reply-To: <453C893E.9060901@devsoft.no>
Jørgen P. Tjernø wrote:
> [ .. a lot of stuff .. ]
It might've been a bit unclear, so here goes:
I'm thinking something like if you read the contents of the file
"/bin/ls" into a buffer, and then want to execute that.
Wouldn't that require that you allocate the memory, do relocation, set
the correct memory page protection (to execute for code, etc), etcetera?
--
Kindest regards / Med vennlig hilsen,
Jørgen P. Tjernø
<jorgen@devsoft.no>
-
To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-10-23 10:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 9:19 execve-type memory-based function, possible? "Jørgen P. Tjernø"
2006-10-23 10:20 ` "Jørgen P. Tjernø" [this message]
2006-10-23 11:33 ` Steve Graegert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=453C975C.1010402@devsoft.no \
--to=jorgen@devsoft.no \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).