This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: about elix
- To: wangwei <wangw at start dot com dot cn>
- Subject: [ECOS] Re: about elix
- From: Fano Ramparany <Fano dot Ramparany at rd dot francetelecom dot fr>
- Date: Fri, 25 May 2001 10:08:02 +0200
- CC: eCos Disuss <ecos-discuss at sourceware dot cygnus dot com>
- Organization: France Telecom
- References: <3B0E0B73.A1B3400C@rd.francetelecom.fr> <001201c0e4ee$ef1739c0$592da8c0@start.com.cn>
- Reply-To: Fano dot Ramparany at rd dot francetelecom dot fr
wangwei wrote:
> I just mean create a thread in the body of anther thread , and the thread
> can use dynamic memory as its
> stack , when the thread ends, the memory of its stack can be released .
> I want to know if ecos support this ?
In the applications I've developped so far thread stacks are preallocated
array variables. Embedded applications generally don't use dynamic memory
management (malloc). eCos provides an alternative mechanism called "memory
pool"
which might fit your needs.
Fano