On 2013-03-13 21:53, Gilles Chanteperdrix wrote: > On 03/13/2013 03:53 PM, Jan Kiszka wrote: > >> In case the application already set a SIGDEBUG handler, let that one >> handle any potential SIGDEBUG_NOMLOCK events and keep our handler >> (xeno_handle_mlock_alert) out of the loop. This helps in scenarios where >> skin libraries are loaded belatedly via dlopen. > > > Another option would be to save the previous handler, and call it when > we detect the signal is not due to an mlock alert.
I've no preference. Pushed that variant now into my queue. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux _______________________________________________ Xenomai mailing list [email protected] http://www.xenomai.org/mailman/listinfo/xenomai
