public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: frysk@sourceware.org
Subject: Re: [SCM]  master: Switch to frysk.sys.ptrace.
Date: Wed, 13 Feb 2008 08:47:00 -0000	[thread overview]
Message-ID: <1202892451.3421.9.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <20080212185049.22237.qmail@sourceware.org>

Hi Andrew,

On Tue, 2008-02-12 at 18:50 +0000, cagney@sourceware.org wrote:
> -        private int peek(long index, byte[] bytes, int offset, int length)
> -	{
> -	  if (mem != null)
> -	    {
> -	      try
> -		{
> -		  return mem.pread(index, bytes, offset, length);
> -		}
> -	      catch (Errno e)
> -		{
> -		  // try again through address space.
> +        private void transfer(long index, byte[] bytes, int offset, int length,
> +			      boolean write) {
> +	    if (mem != null && !write) {
> +		try {
> +		    mem.pread(index, bytes, offset, length);
> +		    return;
> +		} catch (Errno e) {
> +		    // Give up on mem; and fall back to ptrace.  This
> +		    // can happen when /proc isn't mounted, or when a
> +		    // process is terminating and the kernel scrubs
> +		    // the /proc entry before its time.
> +		    mem = null;
>  		}
>  	    }

Are you sure this change is right? The comment is right about those 2
reasons for pread() possibly failing. But I don't believe that is the
only case it can happen. Previously when a read occurred that failed,
possibly because following a pointer in the inferior that was NULL or
not yet initialized that would just cause a error reading from that
particular (uninitialized) memory location. But now whenever that occurs
once for an inferior you blow away mem so pread() can never be used
anymore and we always fall back to having to do single peeks and pokes
through the ptrace address space.

Cheers,

Mark

       reply	other threads:[~2008-02-13  8:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080212185049.22237.qmail@sourceware.org>
2008-02-13  8:47 ` Mark Wielaard [this message]
2008-02-27 11:59   ` Mark Wielaard
2008-03-10 12:02     ` Mark Wielaard

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=1202892451.3421.9.camel@dijkstra.wildebeest.org \
    --to=mark@klomp.org \
    --cc=frysk@sourceware.org \
    /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).