🚀 go-pugleaf

Neil Horman <nhorman@lvl7.com> wrote in message news:<4UTOa.1513$zJ6.1404@fe02.atl2.webusenet.com>...
> Nabeel Shaheen wrote:
> > Hi,
> > 
> > Guys I am stuck with a problem and need some help.
> > 
> > Platform     : Linux(RedHat 7.3)
> > Problem Area : Dynamic Shared Object Libraries, POSIX Threads
> > glibc        : 2.96
> > 
> > Problem:
> > =======
> > The Scenario is such that I have made a module which call a .so file
> > in a new thread and executes it. The .so file has to be provided by
> > the end-user and if that .so gives any runtime-error(SEGFAULTS), the
> > whole process terminates i.e. all the threads executing .so files and
> > more importantly my .so-calling module, which I dont want to be
> > terminated.
> > 
> > so ***IS THERE ANY WAY THAT MY SO-CALLING MODULE DOES NOT TERMINATE
> > DUE TO SOME SEGFAULTS IN A .SO FILE WRITTEN BY THE END-USER OF MY
> > MODULE?***.
> > 
> > Any relevant comment will be appreciated.
> > 
> > Best Regards,
> > 
> > Nabeel Shaheen
> > Sir Syed Research Labs
> > nabsha[at]UNIssuet.edu.pk (remove capitals)
> 
> How about instead of creating a new thread, you re-architect your 
> program to fork a child process to interact with the user supplied 
> shared library?  That way, if the .so file causes a segfault, the child 
> will terminate, but the parent can detect the unclean exit, and inform 
> the user, without needing to shut the whole program down.
> HTH
> Neil

Hi Guys,

Thanx a lot for ur valueable suggestion/information. 

I think Neil is right and therefore am restructuring the application
as this seems to be the only legal way out of this hazardous
environment.

Thanx again for your comments

Best Regards,

Nabeel Shaheen
Sir Syed Research Labs
nabsha[at]UNIssuet.edu.pk (remove capitals)