From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: questions on struct sigcontext
Date: Wed, 12 Dec 2007 11:44:14 -0600 [thread overview]
Message-ID: <47601DEE.4090200@nortel.com> (raw)
Hi all,
First, I'm not subscribed to the list so I'd appreciate being cc'd on
any replies.
We have a project getting started with MIPS, and one of the things that
we're trying to bring in is some exception-handling code that logs
various information about the ways that apps fail.
In particular, the guys working on this have asked for the STATUS,
CAUSE, BADVADDR, and FPC_EIR registers to be made available as part of
struct sigcontext so that they can determine exactly why the app is failing.
Looking at include/asm-mips/sigcontext.h I can see that these registers
appear to be in the struct, but are either marked as "unused" or now
have different names.
Am I correct that these registers are not currently exported to
userspace on a fault? If this is the case, why not? Does anyone have a
patch to enable this export?
It seems odd that mips app designers wouldn't want this information to
be made available.
Any information you can provide would be useful.
Chris
next reply other threads:[~2007-12-12 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 17:44 Chris Friesen [this message]
2007-12-12 18:12 ` questions on struct sigcontext 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
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=47601DEE.4090200@nortel.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox