[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: plugin system
From:       Bavo De Ridder <bavodr () poboxes ! com>
Date:       1999-08-31 16:48:43
[Download RAW message or body]

On Tue, 31 Aug 1999, Matthias Elter wrote:
>On Tue, 31 Aug 1999, Bavo De Ridder wrote:
>> On Tue, 31 Aug 1999, Matthias Elter wrote:
>> >- A shared lib fooling around with canvas data can easily crash KIS.
>> 
>> It this happens than the access interface was not well written. A good
>> interface should make it impossible for a plugin to crash the application.
>> However, the plugin runs in the same address-space as kimageshop, so a division
>> by zero in the plugin will also bring down kimageshop (or a segfault, ....).
>
>Yes thats the problem, but on the other hand:
>- The "official" KIS package will include only stable plugins tested by us.
>- A user probably wont blame _us_  for alpha quality plugin x he found
>on page y crashing his KIS.

I know that LinuxThreads is implemented using the clone() call -> something
like fork + shared memory. Perhaps in this system and with some signal-handlers
one could run a plugin in a seperate thread AND make only the thread crash in
case of problems.

Is there someone here who knows the clone() call and can tell us if the above
scheme could work ????


BDR

[prev in list] [next in list] [prev in thread] [next in thread]