From: u u <userstack@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.6.x.x Execution Process Question
Date: Fri, 8 Jul 2005 22:28:20 -0400 [thread overview]
Message-ID: <96968b4e05070819286482937c@mail.gmail.com> (raw)
Hello,
Im looking for some help on some research I am conducting. Im trying
to understand the complete execution process from start to finish of
an ELF executable object on the i386 platform in particular, but
x86_64 works as well. So far I have come up with the following:
Shell passes arguments and environment to execve() -> sys_execve() ->
do_execve() -> search_binary_handler() -> ?
Is this complete in a very generic way? What specifics happen along the way?
Most of the papers I have found on this are from older kernel versions
2.0 and 2.2. Im trying to find out the specifics of it all, for
example which registers are zeroed out before passing control to
userspace and where it happens. How does the stack look when control
is passed? These types of specifics are what I had in mind.
If anyone can point me in the right direction or provide an
explanation it would be helpful. Thank you.
-us
next reply other threads:[~2005-07-09 2:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-09 2:28 u u [this message]
2005-07-09 9:52 ` Linux 2.6.x.x Execution Process Question Jirka Kosina
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=96968b4e05070819286482937c@mail.gmail.com \
--to=userstack@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.