Re: [ECOS] does ecos support generating core files or kernel crash dumps?

[Adrian Caceres <adrian@atheros.com>]

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.

- 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.
>
>  
>


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss