From: Dirk Eibach <eibach@domain.hid>
To: Xenomai help <xenomai@xenomai.org>
Subject: [Xenomai-help] Resource leaking problem
Date: Fri, 08 Sep 2006 13:44:38 +0200 [thread overview]
Message-ID: <450157A6.80000@domain.hid> (raw)
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 do we have to do in order to clean up all resources properly,
especially if our application is ended by SIGKILL?
Cheers.
--
Dirk Eibach <eibach@domain.hid>
Guntermann & Drunck Systementwicklung GmbH
F & E
Dortmunder Str. 4a, D-57234 Wilnsdorf
Tel.: +49 (0) 2739 8901 100, Fax.: +49 (0) 2739 8901 120
next reply other threads:[~2006-09-08 11:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-08 11:44 Dirk Eibach [this message]
2006-09-08 11:58 ` [Xenomai-help] Resource leaking problem Jan Kiszka
2006-09-08 12:43 ` Gilles Chanteperdrix
[not found] ` <45015E28.7080405@domain.hid>
2006-09-08 12:59 ` (WARNING!!! PGP with incorrect signature) Re: [Xenomai-help] Res Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=450157A6.80000@domain.hid \
--to=eibach@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.