From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28387 invoked by alias); 10 Mar 2004 21:01:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28369 invoked from network); 10 Mar 2004 21:01:14 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 10 Mar 2004 21:01:14 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i2AL1D07029582; Wed, 10 Mar 2004 16:01:13 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i2AL1CM18317; Wed, 10 Mar 2004 16:01:12 -0500 Received: from redhat.com (dhcp-172-16-25-160.sfbay.redhat.com [172.16.25.160]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id i2AL1BR23209; Wed, 10 Mar 2004 13:01:12 -0800 Message-ID: <404F8217.70909@redhat.com> Date: Fri, 19 Mar 2004 00:09:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.4) Gecko/20030922 MIME-Version: 1.0 To: gdb-patches@sources.redhat.com, gdb@sources.redhat.com Subject: Sparc32 Solaris target function calls on stack Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-RedHat-Spam-Score: -4.9 X-SW-Source: 2004-03/txt/msg00252.txt.bz2 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28387 invoked by alias); 10 Mar 2004 21:01:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 28369 invoked from network); 10 Mar 2004 21:01:14 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 10 Mar 2004 21:01:14 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i2AL1D07029582; Wed, 10 Mar 2004 16:01:13 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i2AL1CM18317; Wed, 10 Mar 2004 16:01:12 -0500 Received: from redhat.com (dhcp-172-16-25-160.sfbay.redhat.com [172.16.25.160]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id i2AL1BR23209; Wed, 10 Mar 2004 13:01:12 -0800 Message-ID: <404F8217.70909@redhat.com> Date: Wed, 10 Mar 2004 21:01:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.4) Gecko/20030922 MIME-Version: 1.0 To: gdb-patches@sources.redhat.com, gdb@sources.redhat.com Subject: Sparc32 Solaris target function calls on stack Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-RedHat-Spam-Score: -4.9 X-SW-Source: 2004-03.o/txt/msg00252.txt Message-ID: <20040310210100.uGXPAgG1A3qp0JwF8zWAgHNcVyMvPdoclGB27Nk_dmk@z> 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