[EMAIL PROTECTED] writes:
> With the latest kernel, "crashme +2000.4 3208 200" causes a complete lock-up
> almost immediately (with no diagnostics printed) on my CATS and NetWinder. I
> don't really have time to dig into this at the moment unfortunately but maybe
> someone else would like to take a look.
I cannot get this to provoke a crash on neither the NetWinder, nor the
RiscPC architectures with the as-distributed 2.2.7, no matter what I do.
Could you attempt to provide any information? Since I seem to be unable
to reproduce it, there are several areas that ought to be investigated:
1) Is the crash reproducable by execution of just that line, or does it
require an explicit set of conditions?
2) Is this an as-yet unnoticed bug of the build tools that you are using?
3) There is something different about your configuration/patches which
allows this problem to occur.
4) This is not the exact crashme test that caused the problem - please
follow the guidelines given in the previous instance about reporting
these problems.
The behaviour that I am experiancing is that sp is being corrupted, and
the result is a forced kill by the signal handling code. Having said
that, I think that 2.2.7 may be being overly eager to forcefully kill a
process with invalid stack pointers.
_____
|_____| ------------------------------------------------- ---+---+-
| | Russell King [EMAIL PROTECTED] --- ---
| | | | http://www.arm.linux.org.uk/~rmk/armlinux.html / / |
| +-+-+ --- -+-
/ | THE developer of ARM Linux |+| /|\
/ | | | --- |
+-+-+ ------------------------------------------------- /\\\ |
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
