From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: gdb@sourceware.org
Subject: Re: Disabling stack access for remote targets?
Date: Sun, 03 Jun 2012 16:58:00 -0000 [thread overview]
Message-ID: <20120603165813.GA20143@host2.jankratochvil.net> (raw)
In-Reply-To: <OF2F6B3515.D760FFF8-ONC1257A12.005B31C5-C1257A12.005BC055@transmode.se>
On Sun, 03 Jun 2012 18:42:10 +0200, Joakim Tjernlund wrote:
> Not quite, I don't see memeor attribute "no-access", just ro, wo, and rw.
There is "set mem inaccessible-by-default" for that purpose, default "on",
just do not definy any memory area in that range you do not want to touch.
> Testing for sp == 0 (or sp == ~0) would be much nicer. It would automatically
> disable/enable stack access.
sp == 0 or sp == ~0 are perfectly valid stack addresses on embedded targets.
I have to note I used GDB with embedded targets only very rarely.
Regards,
Jan
next prev parent reply other threads:[~2012-06-03 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 14:29 Joakim Tjernlund
2012-06-03 15:16 ` Jan Kratochvil
2012-06-03 16:42 ` Joakim Tjernlund
2012-06-03 16:58 ` Jan Kratochvil [this message]
2012-06-03 17:21 ` Joakim Tjernlund
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=20120603165813.GA20143@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb@sourceware.org \
--cc=joakim.tjernlund@transmode.se \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).