This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: ptrace PEEKTEXT IO error?!

From: David Lecomber <david at allinea dot com>
To: Daniel Jacobowitz <drow at false dot org>
Cc: gdb <gdb at sources dot redhat dot com>
Date: Wed, 05 Oct 2005 19:34:54 +0100
Subject: Re: ptrace PEEKTEXT IO error?!
References: <1128531841.21837.96.camel@delmo.priv.wark.uk.streamline-computing.com> <20051005171106.GA7835@nevyn.them.org> <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

References:
- ptrace PEEKTEXT IO error?!
  - From: David Lecomber
- Re: ptrace PEEKTEXT IO error?!
  - From: Daniel Jacobowitz
- Re: ptrace PEEKTEXT IO error?!
  - From: David Lecomber

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]