Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Seems like a bug in target_read_stack / dcache_xfer_memory?
Date: Mon, 19 Oct 2009 21:28:00 -0000	[thread overview]
Message-ID: <20091019212817.GB3401@caradoc.them.org> (raw)
In-Reply-To: <4ADCBF6B.9050309@vmware.com>

On Mon, Oct 19, 2009 at 12:35:07PM -0700, Michael Snyder wrote:
>  * The requested location isn't cached, so we return zero.

Simple: that isn't the interface of dcache_xfer_memory.  It should
fill the cache.  Trace it down to dcache_read_line.

> The "until" command tries to read beyond the top of stack,
> which is fine for the running process and fine for the core
> file, but for some reason in this instance wants to go into
> dcache, where nothing currently should be cached.

Beyond the *top*?  And there's something mapped there?

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-10-19 21:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-18 22:37 Michael Snyder
2009-10-18 22:51 ` drow
2009-10-19 17:49   ` Michael Snyder
2009-10-19 18:37     ` Daniel Jacobowitz
2009-10-19 19:41       ` Michael Snyder
2009-10-19 21:28         ` Daniel Jacobowitz [this message]
2009-10-19 21:42           ` Michael Snyder
2009-10-22  2:46             ` Doug Evans
2009-10-22 18:02               ` Michael Snyder
2009-10-22 20:01                 ` Michael Snyder
2009-10-23 17:18                   ` Doug Evans
2009-10-25  2:03                     ` Michael Snyder
2009-10-26  8:25                     ` Hui Zhu
2009-10-19  4:46 ` Hui Zhu
2009-10-19 18:02   ` Michael Snyder

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=20091019212817.GB3401@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.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