RE: [ECOS] System Crash after some hours.

[<ecos-dev at bcsw dot net>]

On a recent project (the first with eCos) we discovered a default option in
eCos that results in a memory leak.  Perhaps it is related to your crash.

Under Infrastructure, there is an option for 'Provide empty C++ delete
functions'.  Make sure it is turned off.  It enabled, all calls to
delete/free do not actually free any memory.  See for a discussion see
'http://sources.redhat.com/ml/ecos-discuss/2002-09/msg00000.html'.  Also,
you can use the mallinfo method to periodically dump out heap information in
case you have a real leak.

I also always set breakpoints at various 'asserts' methods in eCos in order
to be able to look back up the stack for a crash cause.

Hope this helps.

	- Chip Boling

-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Vinayagam
Sent: Friday, October 29, 2004 2:44 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] System Crash after some hours.

Hi,

I am doing porting eCos to an Intel XScale PXA-255 based board used for
Audio/Video Streaming Application.



We have problem in long run test. The problem is that eCos 2.0 started to
crash our system, sometimes after some ours. This is a serious issue as far
as our system concerned.

We have tried with GCC 3.2.1 & GCC 3.2.2 but the problem still exist in our
system. I am hanging around this issue past two weeks.



Any ideas what might be the problem?



Thanks in Advance.

Regards,

Vinayagam.M


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







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