Re: faults in dynamic libraries

[jnf <xjnfx@doityourself.com>]

not much better, but if one created a plugin manager type process that dealt with them all, it would keep the main process from dying if a plugin died? 

--- Glynn Clements <glynn.clements@virgin.net> wrote:
>
>Tver Mit wrote:
>
>> 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?
>
>If a plugin shares its address space with the main program, a bug can
>corrupt that address space, killing the main program.
>
>Running plugins in a separate process is the only reliable mechanism,
>but it probably isn't practical. Even then, a plugin may still be able
>to interfere with the main process if they share system resources such
>as file descriptors.
>
>-- 
>Glynn Clements <glynn.clements@virgin.net>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

_____________________________________________________________
Sign up for FREE email from DoItYourself.com at http://doityourself.com

_____________________________________________________________
Promote your group and strengthen ties to your members with email@yourgroup.org by Everyone.net  http://www.everyone.net/?btn=tag