From: Tver Mit <Vukdev@mail.ru>
To: linux-c-programming@vger.kernel.org
Subject: faults in dynamic libraries
Date: Thu, 13 Jun 2002 13:45:24 +0400 [thread overview]
Message-ID: <1746252115.20020613134524@mail.ru> (raw)
Hi all.
I write a programm that uses plugins (on dl* functions base). When plugin code is free of
bugs all is ok, but when plugin faults by any reason, my programm do so. I want my programm
to work even if plugin dies. I see two ways:
1. handling signals
2. run plugin in different thread or process
but then:
in 1. what will be with resources, that plugin use ?
in 2. it'll be about 15-20 plugins running - so there will be 15-20 processes. And how to synchronise them all?
Got any ideas, opinions?
________________
Good hunt.
Tver mailto:Vukdev@mail.ru
next reply other threads:[~2002-06-13 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 9:45 Tver Mit [this message]
2002-06-13 11:52 ` faults in dynamic libraries Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2002-06-16 10:50 jnf
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=1746252115.20020613134524@mail.ru \
--to=vukdev@mail.ru \
--cc=linux-c-programming@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).