All of lore.kernel.org
 help / color / mirror / Atom feed
From: kkonaka@mac.com
To: glynn.clements@virgin.net
Cc: linux-c-programming@vger.kernel.org
Subject: Re: stack -> PROT_EXEC/why?
Date: Mon, 05 Aug 2002 10:21:47 -0400	[thread overview]
Message-ID: <sqb8z3lpero.wl@nue.mac.com> (raw)
In-Reply-To: <15694.23819.46199.920521@cerise.nosuchdomain.co.uk>

> It is sometimes necessary to execute dynamically generated code which
> is placed on the stack. The most common cases are in handling signals,
> in a technique called a "trampoline" (this is mentioned in the gcc
> Info file), and some emulators (e.g. Executor, the Mac emulator).

thank you very much - this helps me a lot.

> Yes. There is a patch available to change this, but in the standard
> kernel, the primary stack is executable.

I'll try {locate/}take a look :)

> It isn't portable, but you can get this information from
> /proc/<pid>/maps.

tested with my mini-test program - serves the purpose fine :)

thanks again!
kenji

      reply	other threads:[~2002-08-05 14:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05  1:22 stack -> PROT_EXEC/why? kkonaka
2002-08-05 11:10 ` Glynn Clements
2002-08-05 14:21   ` kkonaka [this message]

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=sqb8z3lpero.wl@nue.mac.com \
    --to=kkonaka@mac.com \
    --cc=glynn.clements@virgin.net \
    --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 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.