Re: Seems like a bug in target_read_stack / dcache_xfer_memory?

Michael Snyder
2009-10-19T21:42:06Z

Daniel Jacobowitz wrote:
> 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.

Well that's what it does.

>
>> 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?

Arr, you know, "top" as in "TOS", as in the next location
that would be used if you pushed something.

Anyway, yes, that's what it does. dcache returns zero,
and memory_xfer_partial bails out instead of trying the
next target down the target stack.