public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001673] New: extra information for exception dump
Date: Tue, 18 Sep 2012 23:23:00 -0000 [thread overview]
Message-ID: <bug-1001673-13@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email. Use the web interface provided at:
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001673
Summary: extra information for exception dump
Product: eCos
Version: 3.0
Platform: All
OS/Version: ARM
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: HAL
AssignedTo: unassigned@bugs.ecos.sourceware.org
ReportedBy: jo.lin@sunplusmedia.com
CC: ecos-bugs@ecos.sourceware.org
Class: Advice Request
Created an attachment (id=1938)
--> (http://bugs.ecos.sourceware.org/attachment.cgi?id=1938)
solution for extra information
Overview: More detailed exception information.
1.
Some series of ARM supports FSR (Fault Status Register) and FAR (Fault
Address Register) that give us a precise cause for 2 specify exception
(prefetch abort and data abort).
We have a proposal to dump that kind information when
CYGHWR_HAL_ARM_DUMP_EXCEPTIONS enable.
2.
We were under obligation to provide the spsr information also in case we
cannot guarantee one situation that an unpredicted exception raises during
exception handling.
3.
Our development group team has a tool for investigation all the data in
stack, the amount of data to determines the reliability of the results, we are
suggest to provide a flexible buffer size.
--
Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-09-18 23:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 23:23 bugzilla-daemon [this message]
2012-09-18 23:23 bugzilla-daemon
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=bug-1001673-13@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-bugs@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).