Re: (WARNING!!! PGP with incorrect signature) Re: [Xenomai-help] Res

[Jan Kiszka <jan.kiszka@domain.hid>]

[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]

Dirk Eibach wrote:
> jan.kiszka@domain.hid wrote:
>> Dirk Eibach wrote:
>>> Hello,
>>>
>>> we have lots of tasks, semaphores and mutexes in our complex
>>> application. Stopping and restarting seems to leak some resources,
>>> because we get ENOMEM when a thread is created after restarting the
>>> application, first time everything goes well.
>>>
>>> Probably we do something wrong, maybe somebody can tell us what.
>>
>> What skin do you use? Native? Only the POSIX skin currently does
>> auto-cleanup, the others require explicit care.
> 
> We are using native skin, so that explains the problem we are facing.
> Thanks.
> 
>>> What do we have to do in order to clean up all resources properly,
>>> especially if our application is ended by SIGKILL?
>>
>> Install a signal handler and do cleanup of all allocated objects (tasks
>> get deleted when they terminate). Either keep track of your allocated
>> resources in some list(s) or signal the owners (tasks) that they should
>> terminate and cleanup their locally allocated resources. There are
>> dozens of ways to do this, depending on your application design.
>>
>> But if you think that you are cleaning up correctly and still face
>> leaks, try to derive a simple test that demonstrates the issue.
> 
> Hmmm, wouldn't it be clever to have a syscall that would allow us to
> free all xenomai resources at once, so we could call it on application
> startup? Otherwise SIGKILL will still be a problem.

Actually, the per-process cleanup is what we should head for also under
the other skins. It will also address SIGKILL (which cannot be caught by
a handler, of course). As most of us only have one brain to think and
two hands to hack, and those are also shared resources ;), support is
always welcome.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]