From: Mark Salter <msalter@redhat.com>
To: sjohnson@neurizon.net
Cc: drow@false.org, gdb@sources.redhat.com
Subject: Re: GDB and ARM Frame Pointer strangeness
Date: Tue, 08 Jun 2004 12:26:00 -0000 [thread overview]
Message-ID: <20040608122635.35BD37907B@deneb.localdomain> (raw)
In-Reply-To: <40C54834.4080408@neurizon.net> (message from Steven Johnson on Tue, 08 Jun 2004 15:01:40 +1000)
>>>>> 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
next prev parent reply other threads:[~2004-06-08 12:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 8:50 Steven Johnson
2004-06-08 4:25 ` Steven Johnson
2004-06-08 4:29 ` Daniel Jacobowitz
2004-06-08 5:02 ` Steven Johnson
2004-06-08 12:26 ` Mark Salter [this message]
2004-06-08 23:47 ` Steven Johnson
2004-06-09 15:14 ` Andrew Cagney
2004-06-10 0:06 ` Steven Johnson
2004-06-10 2:20 ` Ian Lance Taylor
2004-06-10 4:37 ` Steven Johnson
2004-06-10 5:10 ` Ian Lance Taylor
2004-06-10 7:16 ` Steven Johnson
2004-06-10 21:32 ` Andrew Cagney
2004-06-11 0:46 ` Steven Johnson
2004-06-11 15:33 ` Andrew Cagney
2004-06-10 9:03 ` Richard Earnshaw
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=20040608122635.35BD37907B@deneb.localdomain \
--to=msalter@redhat.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=sjohnson@neurizon.net \
/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