[ECOS] code fatal error!

[ECOS] code fatal error!

[张 亮]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb2312; format=flowed, Size: 545 bytes --]


Hi,all!
     in eCos,kill() function does not release mutex owned by thread which 
will be killed. I think it as a fatal error.right? or more wise machanism 
avoids this state?

tks&regards!
 
                                                              johnsonest


_________________________________________________________________
Ãâ·ÑÏÂÔØ MSN Explorer: http://explorer.msn.com/lccn/


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

Re: [ECOS] code fatal error!

[Martin Buck]

ÕÅ ÁÁ wrote:
>      in eCos,kill() function does not release mutex owned by thread which
> will be killed.

Neither does it free its allocated memory, close its open files, etc.
Why should it release its mutexes?

> I think it as a fatal error.right?

Yes, a fatal programmer error. You're supposed to read the documentation
first.

> or more wise machanism
> avoids this state?

Send the thread a message asking it to clean up and terminate itself.

Martin

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

Re: [ECOS] code fatal error!

[Nick Garnett]

张 亮 <johnsonest@hotmail.com> writes:

> Hi,all!
>      in eCos,kill() function does not release mutex owned by thread
> which will be killed. I think it as a fatal error.right? or more wise
> machanism avoids this state?
> 

If a thread owns a mutex it is presumably for a reason -- to protect
some data against concurrent access. If you just kill a thread you are
likely to leave that data in an inconsistent state. Releasing the
mutex does nothing to solve this problem, it just exposes the
inconsistent data to other threads. 

The correct approach, as others have mentioned, is to arrange for
threads to shut themselves down in an orderly fashion. 

-- 
Nick Garnett - eCos Kernel Architect


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

[ECOS] bridge in LWIP ?

[peter_ku]

Hi,

I am using lwip now. But I found there is no bridge function in lwip package. but supported in TCP/IP package.
If I need bridge function in lwip, anyone have suggestion?

thanks a lot for support.


Peter