From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21904 invoked by alias); 8 Jun 2004 12:26:40 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 21871 invoked from network); 8 Jun 2004 12:26:37 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 8 Jun 2004 12:26:37 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i58CQai5023978 for ; Tue, 8 Jun 2004 08:26:36 -0400 Received: from pobox.corp.redhat.com (pobox.corp.redhat.com [172.16.52.156]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i58CQa002274; Tue, 8 Jun 2004 08:26:36 -0400 Received: from deneb.localdomain (msalter.cipe.redhat.com [10.0.0.36]) by pobox.corp.redhat.com (8.12.8/8.12.8) with ESMTP id i58CQZ17002072; Tue, 8 Jun 2004 08:26:36 -0400 Received: by deneb.localdomain (Postfix, from userid 500) id 35BD37907B; Tue, 8 Jun 2004 08:26:35 -0400 (EDT) From: Mark Salter To: sjohnson@neurizon.net Cc: drow@false.org, gdb@sources.redhat.com In-reply-to: <40C54834.4080408@neurizon.net> (message from Steven Johnson on Tue, 08 Jun 2004 15:01:40 +1000) Subject: Re: GDB and ARM Frame Pointer strangeness References: <40C42C75.5020208@neurizon.net> <40C53F70.8030101@neurizon.net> <20040608042936.GA7514@nevyn.them.org> <40C54834.4080408@neurizon.net> Message-Id: <20040608122635.35BD37907B@deneb.localdomain> Date: Tue, 08 Jun 2004 12:26:00 -0000 X-SW-Source: 2004-06/txt/msg00050.txt.bz2 >>>>> Steven Johnson writes: > I have yet to come across a stub that validates memory addresses. Stubs > are usually Lean and Mean. What criteria would a stub use to validate > the memory addresses? Pretty much all of the ones I have seen are protected against bad memory accesses. For instance, RedBoot stubs use the most usual mechanism whereby a fault handler is used to catch accesses which throw a cpu exception. The stub is in a much better position to determine if a memory space access is valid or not. GDB only knows about memory occupied by the program being debugged. A user may also want to access h/w registers at addresses not known by GDB. --Mark