Memory management between threads in RTEMS

[Thomas Doerfler]

Till,

Am 18.07.2012 16:45, schrieb Till Straumann:
> The memory allocator is indeed protected by the system,
> i.e., two threads may each call 'malloc()' without having
> to worry that the heap gets messed up.
> 
> If you talk about protecting some allocated memory from
> concurrent access by multiple threads then you do that
> in the usual way, e.g., by using a mutex.

maybe I got that question wrong, but I have interpreted it as: How do I
make sure I don't mess up a different thread's private memory
inadvertedly, e.g. by a "wild running pointer"...

wkr,

Thomas.

> 
> - Till
> 
> On 07/18/2012 09:27 AM, Thomas Doerfler wrote:
>> Hi,
>>
>> up to now, there is no general concept to do this in RTEMS. Some ideas
>> are discussed to cover part of these requirements...
>>
>> Part of the problem is that memory like static variables, heap, OS
>> workspace in general is managed gobally.
>> wkr,
>>
>> Thomas.
>>
>> Am 18.07.2012 16:20, schrieb m.shahverdi:
>>> Hi,
>>> I have an application with two threads but I don't know how to protect
>>> memory of each thread against other thread.please help me.
>>>
>>> thanks
>>>
>>>
>>>
>>> _______________________________________________
>>> rtems-users mailing list
>>> rtems-users at rtems.org
>>> http://www.rtems.org/mailman/listinfo/rtems-users
>>>
>>
>>
> 
> 
> _______________________________________________
> rtems-users mailing list
> rtems-users at rtems.org
> http://www.rtems.org/mailman/listinfo/rtems-users



-- 
--------------------------------------------
embedded brains GmbH
Thomas Doerfler
Obere Lagerstrasse 30
D-82178 Puchheim
Germany
email: Thomas.Doerfler at embedded-brains.de
Phone: +49-89-18908079-2
Fax: +49-89-18908079-9
PGP: Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.