True. For the old ppc code, the problem occurs with any other signal
as well, but the signal stack problem is specific to SIGSEGV and
possibly SIGBUS, depending on architecture.
> In any case, there are all sorts of things that could go wrong and
> leave the process stuck in an infinite loop. If you really want a
> core dump when things go wrong then you probably need some sort of
> watchdog process plus a way for one process to force another to dump
> core and exit (like a SIGKILL but with a core dump as well).
That would be optimal, yes. This external core dump signal doesn't
exist yet, does it?
> You haven't convinced me that the kernel is doing anything wrong or
> even suboptimal - it seems to me that you have run into some
> unintended consequences of your code, that's all. You can't expect
> the kernel to work around all the bugs in your user processes. :)
Correct. The userspace will have bugs and it will have plenty. The
interesting question is only, if we can gather enough debugging data
to identify and fix those bugs, when they occur. This is embedded, no
user is going to narrow down the problem.
Jörn
-- A defeated army first battles and then seeks victory. -- Sun Tzu - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/