From: Daniel Jacobowitz <dan@debian.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: questions on struct sigcontext
Date: Thu, 13 Dec 2007 10:36:21 -0500 [thread overview]
Message-ID: <20071213153621.GA32600@caradoc.them.org> (raw)
In-Reply-To: <47607327.5090709@nortel.com>
On Wed, Dec 12, 2007 at 05:47:51PM -0600, Chris Friesen wrote:
> If the cause/badvaddr entries in struct sigcontext were filled in by the
> exception handler in the kernel, wouldn't the values in that struct be
> completely valid even if the registers themselves were changed before
> userspace could handle the signal?
Yeah, my reply didn't make much sense. Trust Ralf's instead.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2007-12-13 19: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
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 [this message]
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=20071213153621.GA32600@caradoc.them.org \
--to=dan@debian.org \
--cc=cfriesen@nortel.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.