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@xxxxxxxxxxx mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
GIOVE A Transmits Loud And Clear ...GIOVE A Transmits Loud And Clear ... After a successful launch on 28 December 2005, ... currently being performed to check the quality of these signals.... (sci.geo.satellite-nav)
Re: Code used to protect missile commands? ... There are unjammable signals, and signals which use line of ... On a live bird there is none. ... know that have commanded combat missile crews over the past ... including launching on you and then, ... (sci.crypt)
Re: Radio Communication to Start Launch ... person from the wing runner.... what limitations you're facing that prevents the tow pilot from seeing ...launch unassisted.... the standard SSA signals, should not be left unassisted to launch a glider. ... (rec.aviation.soaring)
