public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Adrian Caceres <adrian@atheros.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] does ecos support generating core files or kernel crash dumps?
Date: Wed, 15 Oct 2003 20:43:00 -0000	[thread overview]
Message-ID: <1066250632.32461.89.camel@hermes> (raw)
In-Reply-To: <3F8DB002.9090800@atheros.com>

On Wed, 2003-10-15 at 14:37, Adrian Caceres wrote:
> Many embedded systems have  a local/ide type bus
> to a flash.  Assuming the basic driver to such interface was not affected
> by the crash, it would be possible to write a dump to it.
> Or there might be some storage available across some network
> interface.  The embedded system
> could send the crash dump over to the other end for storage.
> 
> Having gdb support is great for development, but when it comes
> to beta,  a core dump can be more useful.  It is not rare for
> a specific problem to only occur at some beta site and there
> is simply no way to gdb to it.  The serial port might not even
> be stuffed or accesible in these units.  But give them a unit
> with an extra large flash, wait for the problem to happen again,
> get the unit back,  and now you might have all the information you need.
> If the embedded device already has a removable flash such
> as a digital or video camera,  the process is simply a swap of
> a flash.
> 

These are wonderful arguments (I made the same ones more than 25
years ago to my boss at the time...).  The infrastructure is all
there for you to add such a capability, it's just not something
that has ever been done before.

As for your first statement about having a local IDE bus with
FLASH - that's probably less than 2% of all of the systems that
eCos is normally deployed on, but if you've got it, flaunt it!

> - adrian
> 
> Gary Thomas wrote:
> 
> >On Wed, 2003-10-15 at 11:28, Adrian Caceres wrote:
> >  
> >
> >>I am wondering if ecos already supports generating core files or crash
> >>dumps for post-mortem analysis using gdb.
> >>    
> >>
> >
> >No.  Where would you put them [in an embedded system]?
> >
> >If the application "crashes", just connect to it using GDB
> >and figure out why.
> >
> >  
> >
-- 
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

      reply	other threads:[~2003-10-15 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 17:29 Adrian Caceres
2003-10-15 18:08 ` Gary Thomas
2003-10-15 20:37   ` Adrian Caceres
2003-10-15 20:43     ` 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=1066250632.32461.89.camel@hermes \
    --to=gary@mlbassoc.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).