Date: Wed, 25 Jan 2006 10:46:30 -0800 From: Julian Elischer <julian@elischer.org> To: Jose Marcio Martins da Cruz <Jose-Marcio.Martins@ensmp.fr> Cc: freebsd-hackers@freebsd.org Subject: Re: Changes from 5.2.1 to 5.3 (theads / signal handling) Message-ID: <43D7C786.1090803@elischer.org> In-Reply-To: <43D74F91.2090009@ensmp.fr> References: <43D74F91.2090009@ensmp.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Jose Marcio Martins da Cruz wrote: >Hello, > >I have a problem with an application I wrote. > >It works fine under Solaris, Linux, and FreeBSD till release 5.2.1. > >Under FreeBSD 5.3 and newers I have problems. > >The application is constituted by two processes : a supervisor and modules. The >supervisor forks and become a module when it shall launch one. > >The supervisor is a single loop and it has a thread to handle signals. Each >module is a multithreaded server, with its own thread to handle signals. > >Under FreeBSD 5.3 and newers, when the supervisor forks to become a module, it >receives a SIGABRT and exits immediately when it launches the signal handler thread. > >I solved this by replacing the signal handling of the father : using a handler >defined with sigaction instead of using a thread. But I'd like to understanding >what's wrong with this and what changed from FreeBSD 5.2.1 to 5.3 > > a new threading library. have you tried 6.0? also, does the child do an exec() after forking? >Thanks > >Jose-Marcio >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43D7C786.1090803>