remote connection crash, was frame theory

[Daniel Jacobowitz]

On Thu, Jan 26, 2006 at 05:26:10PM -0600, NZG wrote:
> > The best thing here would be, if the stub can find out from
> > the kernel what constitutes "valid" RAM, to refuse reads to
> > it.  Then ignore the ugliness when you type backtrace and
> > don't have a stack yet - it's not real surprising that doesn't
> > work!

Can you do this?  It is the most reliable way to prevent the oops and
will continue to do so in other circumstances, e.g. stupid users and
bad pointers.

> Stepping through the code I can see that remote_fetch_registers is never 
> called before this crash happens, all the data being used in the backtrace 
> appears to be transferred in the initial connection and cached.

Did you look at the remote protocol output (set debug remote 1)? 
Several registers are usually transfered in the initial connection,
e.g. sp and pc.  It's just an optimization.

-- 
Daniel Jacobowitz
CodeSourcery