From: Michael Snyder <msnyder@redhat.com>
To: gdb-patches@sources.redhat.com, gdb@sources.redhat.com
Subject: Sparc32 Solaris target function calls on stack
Date: Wed, 10 Mar 2004 21:01:00 -0000 [thread overview]
Message-ID: <404F8217.70909@redhat.com> (raw)
Message-ID: <20040310210100.uGXPAgG1A3qp0JwF8zWAgHNcVyMvPdoclGB27Nk_dmk@z> (raw)
Is anyone planning on converting the sparc32 target over to use
a target-function-call scheme similar to that of sparc64? ie. so
that it doesn't have to execute code on the stack?
Apparently there is a security setting on Solaris that prohibits
executing code on the stack, even on sparc32, to reduce the risk
of being hacked into, and I'm guessing more and more companies are
going to be adopting it in these uncertain times.
Michael
next reply other threads:[~2004-03-10 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Michael Snyder [this message]
2004-03-10 21:01 ` Michael Snyder
2004-03-10 21:52 ` Andrew Cagney
2004-03-19 0:09 ` Andrew Cagney
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=404F8217.70909@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
/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