From: David Lecomber <david@allinea.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb <gdb@sources.redhat.com>
Subject: Re: ptrace PEEKTEXT IO error?!
Date: Wed, 05 Oct 2005 18:40:00 -0000 [thread overview]
Message-ID: <1128537294.27899.0.camel@delmo.priv.wark.uk.streamline-computing.com> (raw)
In-Reply-To: <1128536411.21837.123.camel@delmo.priv.wark.uk.streamline-computing.com>
On Wed, 2005-10-05 at 19:20 +0100, David Lecomber wrote:
>
> It seems ok at reading memory from addresses on the heap and stack --
> but it barfs at reading memory from the text segment. Is there
> something that the user code (one of the libraries called by my
> program) could do to prevent access to memory by a ptracing program?
>
and I should have asked.. or is it only possible for the kernel, or a
kernel module to do that?
Cheers
David
--
David Lecomber, CTO, Allinea Software
tel: +44 1926 623231 fax: +44 1926 623232
next prev parent reply other threads:[~2005-10-05 18:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 17:10 David Lecomber
2005-10-05 17:11 ` Daniel Jacobowitz
2005-10-05 18:26 ` David Lecomber
2005-10-05 18:40 ` David Lecomber [this message]
2005-10-05 18:41 ` Daniel Jacobowitz
2005-10-05 19:50 ` David Lecomber
2005-10-05 19:54 ` Daniel Jacobowitz
2005-10-05 20:31 ` David Lecomber
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=1128537294.27899.0.camel@delmo.priv.wark.uk.streamline-computing.com \
--to=david@allinea.com \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
/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).