Jeff Dike <jdike@karaya.com> writes:
> This is how I handle it. It requires no setup at handler
> registration time (not that I did on purpose, anyway).
You misunderstood my question.
I want to know what address was being accessed to cause the fault, not
the address of the faulting instruction. The information I am looking
for does not exist in the struct sigcontext, but it does exist in the
siginfo_t. See the man page for sigaction(2), particularly the
description of the si_addr field. Then examine the handling of the
si_addr field in the kernel sources under arch/m68k and compare with
arch/i386.
Unless this information is just not available on the i386 architecture
(I do not know enough about it to be sure), I think this is a bug in
the kernel.
- Pat
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jan 15 2000 - 21:00:11 EST