From: Andrew Cagney <cagney@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Sparc32 Solaris target function calls on stack
Date: Wed, 10 Mar 2004 21:52:00 -0000 [thread overview]
Message-ID: <404F44F3.8010009@gnu.org> (raw)
In-Reply-To: <404F8217.70909@redhat.com>
> 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.
This is from the NEWS file for 6.1:
> * Revised SPARC target
>
> The SPARC target has been completely revised, incorporating the
> FreeBSD/sparc64 support that was added for GDB 6.0. As a result
> support for LynxOS and SunOS 4 has been dropped. Calling functions
> from within GDB on operating systems with a non-executable stack
> (Solaris, OpenBSD) now works.
It should be working?
Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <cagney@gnu.org>
To: Michael Snyder <msnyder@redhat.com>
Cc: gdb-patches@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: Sparc32 Solaris target function calls on stack
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <404F44F3.8010009@gnu.org> (raw)
Message-ID: <20040319000900.9y8XtcHqrM_ptCCtw4818Ea3KJRGrskaIPhNJOFCPlE@z> (raw)
In-Reply-To: <404F8217.70909@redhat.com>
> 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.
This is from the NEWS file for 6.1:
> * Revised SPARC target
>
> The SPARC target has been completely revised, incorporating the
> FreeBSD/sparc64 support that was added for GDB 6.0. As a result
> support for LynxOS and SunOS 4 has been dropped. Calling functions
> from within GDB on operating systems with a non-executable stack
> (Solaris, OpenBSD) now works.
It should be working?
Andrew
next prev parent reply other threads:[~2004-03-10 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Michael Snyder
2004-03-10 21:01 ` Michael Snyder
2004-03-10 21:52 ` Andrew Cagney [this message]
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=404F44F3.8010009@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=msnyder@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