From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28171 invoked by alias); 1 Jun 2012 14:29:37 -0000 Received: (qmail 28162 invoked by uid 22791); 1 Jun 2012 14:29:37 -0000 X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_40,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from gw1.transmode.se (HELO gw1.transmode.se) (195.58.98.146) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 01 Jun 2012 14:29:25 +0000 Received: from mail1.transmode.se (mail1.transmode.se [192.168.201.18]) by gw1.transmode.se (Postfix) with ESMTP id 0903F258146 for ; Fri, 1 Jun 2012 16:29:24 +0200 (CEST) Subject: Disabling stack access for remote targets? X-KeepSent: 32191D46:36EDC2F3-C1257A10:004B2D80; type=4; name=$KeepSent To: gdb@sourceware.org Message-ID: From: Joakim Tjernlund Date: Fri, 01 Jun 2012 14:29:00 -0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII 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/msg00001.txt.bz2 Debugging u-boot/bios direcly from reset using remote gdb can be a challenge. One reason is that gdb insists on reading stack contents each time it stops execution. 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 Jocke