| To: | Chris Friesen <cfriesen@nortel.com> |
|---|---|
| Subject: | Re: questions on struct sigcontext |
| From: | David Daney <ddaney@avtrex.com> |
| Date: | Wed, 12 Dec 2007 10:44:14 -0800 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <476029AB.80702@nortel.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <47601DEE.4090200@nortel.com> <47602471.9080706@avtrex.com> <476029AB.80702@nortel.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Thunderbird 1.5.0.12 (X11/20071019) |
Chris Friesen wrote: David Daney wrote:Most of the information is available. The si_addr and si_code of the sigcontext are populated as well as the ucontext at the fault.I assume this should be siginfo rather than sigcontext? Yes. In the three parameter form of the signal handler the second and third parameters are pointers to the siginfo and ucontext. Given all this and the code at $pc when the fault occurred, it is a simple matter to determine what happened.Okay. I'll pass that information on and see if it's sufficient. Thanks, Chris |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: questions on struct sigcontext, Chris Friesen |
|---|---|
| Next by Date: | Re: questions on struct sigcontext, Ralf Baechle |
| Previous by Thread: | Re: questions on struct sigcontext, Chris Friesen |
| Next by Thread: | Re: questions on struct sigcontext, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |