From: "Dirk Broer" <dbroer@matrics.com>
To: "ECOS" <ecos-discuss@sources.redhat.com>
Subject: [ECOS] Unexpected exception handler call (0x53)
Date: Mon, 24 Nov 2003 04:48:00 -0000 [thread overview]
Message-ID: <EFEEIJLMMJEMDAEMCNIGOEKBCLAA.dbroer@matrics.com> (raw)
We are newly targeting an arm based board.
We get often an exception with 0x53 (83).
Back Trace shows nothing interesting.
How best to proceed to track this down? Where would the Âreal stack have
been stored? Was it stored?
My best guess is that this is the default handler, should we override this?
Again, can we recover the stack?
We are still implementing Âinfo threads and right now have no direct
visibility on the state of other threads in the system.
__ __ ___ ________ ___ __ ___ ___
Dirk Broer / ||/ || /_ || /__ __// /__ \\ /// /__ \\ / __\\
//||//||| ///||| /// ///_/// __ /// ||| ///_
///| //||| /___ || /// /__ // /// /// /__ ||
/// |// ||| /// ||| /// /// ||| /// ///__/// ____///
/// |||/// |||/// /// ||| /// |____// /____//
Software Engineer
(410)872-0300
#include <standard_disclaimer>
#include <funny_quote>
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next reply other threads:[~2003-11-24 4:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 4:48 Dirk Broer [this message]
2003-11-24 14:16 ` Nick Garnett
2003-11-24 14:57 ` [ECOS] help for building microwindows centraility_liu
2003-11-24 15:01 ` Gary Thomas
2003-11-24 15:05 ` alfred
2003-11-24 15:08 ` Gary Thomas
2003-11-24 15:13 ` alfred
2003-11-24 15:19 ` alfred
2003-11-24 15:23 ` Gary Thomas
2003-11-24 15:21 ` Gary Thomas
2003-11-24 15:28 ` alfred
2003-11-24 15:32 ` Gary Thomas
2003-11-24 15:49 ` alfred
2003-11-24 15:53 ` alfred
2003-11-24 16:09 ` Gary Thomas
2003-11-24 16:22 ` alfred
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=EFEEIJLMMJEMDAEMCNIGOEKBCLAA.dbroer@matrics.com \
--to=dbroer@matrics.com \
--cc=ecos-discuss@sources.redhat.com \
/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).