From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31798 invoked by alias); 3 Jun 2012 15:16:26 -0000 Received: (qmail 31782 invoked by uid 22791); 3 Jun 2012 15:16:24 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 03 Jun 2012 15:16:09 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q53FG783020490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 3 Jun 2012 11:16:07 -0400 Received: from host2.jankratochvil.net (ovpn-116-47.ams2.redhat.com [10.36.116.47]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q53FG37C028968 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 3 Jun 2012 11:16:06 -0400 Date: Sun, 03 Jun 2012 15:16:00 -0000 From: Jan Kratochvil To: Joakim Tjernlund Cc: gdb@sourceware.org Subject: Re: Disabling stack access for remote targets? Message-ID: <20120603151603.GA16834@host2.jankratochvil.net> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2012-06/txt/msg00017.txt.bz2 On Fri, 01 Jun 2012 16:29:23 +0200, Joakim Tjernlund wrote: > This can be devastating for a board that hasn't initialized RAM yet. > Would it be possible for a remote target to inform gdb not to touch the > stack? In its simplest form one could just test for sp == 0 I guess you want: $ info '(gdb)Memory Region Attributes' Regards, Jan