From: David Daney <ddaney@avtrex.com>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-mips@linux-mips.org
Subject: Re: questions on struct sigcontext
Date: Wed, 12 Dec 2007 10:44:14 -0800 [thread overview]
Message-ID: <47602BFE.4050606@avtrex.com> (raw)
In-Reply-To: <476029AB.80702@nortel.com>
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
next prev parent reply other threads:[~2007-12-12 18:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 17:44 questions on struct sigcontext Chris Friesen
2007-12-12 18:12 ` David Daney
2007-12-12 18:34 ` Chris Friesen
2007-12-12 18:44 ` David Daney [this message]
2007-12-12 18:57 ` Ralf Baechle
2007-12-12 19:00 ` Daniel Jacobowitz
2007-12-12 19:04 ` Ralf Baechle
2007-12-12 23:47 ` Chris Friesen
2007-12-13 0:06 ` David Daney
2007-12-13 15:36 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47602BFE.4050606@avtrex.com \
--to=ddaney@avtrex.com \
--cc=cfriesen@nortel.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox