From: Gary Thomas <gary@mlbassoc.com>
To: Reinhard JESSICH <Reinhard.JESSICH@frequentis.com>
Cc: adrian@atheros.com, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] does ecos support generating core files or kernel crashdumps?
Date: Thu, 16 Oct 2003 11:54:00 -0000 [thread overview]
Message-ID: <1066305281.32461.112.camel@hermes> (raw)
In-Reply-To: <sf8e6474.098@mail.frequentis.com>
On Thu, 2003-10-16 at 01:27, Reinhard JESSICH wrote:
> Hello
>
> We had similar needs for our development.
> As you know we have implemented a process model and memory protection
> for the PowerPC. We also implemented the first step of a core dump feature.
>
> If an exception occures (dived by zero, illegal read/write, assert, ... ), we write
> the exception text, the thread, the registers, a stackdump of the running thread
> and if this is not possible a stackdump of the interrupt stack. The stackdump is
> not a simple memory dump, but the context of each called function. This allowes
> us to see the call graph and the exact position where the exception occures very
> easily. We write the whole information to an unused memory, which is not erased
> during reset. We can store as much core dumps as memory is available.
> After reset we can read the core's via telnet or serail line.
>
> We plan to store the complete context of the thread and its memory in
> compressed form. This allowes us to see the content of variables in gdb. This would
> be a real core feature. If it is too big for the unused memory, we can store it on a
> flash.
>
> We have submitted a patch for our process extension, but EcosCentric does not
Just a fine point - eCosCentric [itself] has nothing to do with this
decision. These choices are made by the eCos maintainers, who
themselves [hopefully] represent the eCos community as a whole.
> accept it. If you are interrested, search in the archives for memory protection.
> The patch was submitted by my colleague Thomas Binder.
> You will find the core code there. In the meantime we have continued the
> development, but this parts should be still the same.
>
> Best regards,
> Reinhard
>
>
> --
> Ing. Reinhard Jessich Phone: +43/1/81150/2395
> Software Design Fax: +43/1/81150/3169
> Frequentis Nachrichtentechnik GmbH A-1120 Wien, Spittelbreitengasse 34
> http://www.frequentis.com eMail: reinhard.jessich@frequentis.com
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
prev parent reply other threads:[~2003-10-16 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-16 7:27 Reinhard JESSICH
2003-10-16 11:54 ` Gary Thomas [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=1066305281.32461.112.camel@hermes \
--to=gary@mlbassoc.com \
--cc=Reinhard.JESSICH@frequentis.com \
--cc=adrian@atheros.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).