Gilles Chanteperdrix wrote: > Gilles Chanteperdrix wrote: >> Philippe Gerum wrote: >>> Well, what about merging the solutions: trap the signal from the library >>> constructor by default for people relying on #1, AND document the shadow >>> signal >>> handler for people who can do #2? >> For me, merging the two, would mean keep sigshadow_install called upon >> thread creation, but export xeno_sigwinch_handler to be callable from >> user signals. >> >> This way, if people install their signal handler before the first thread >> creation, they have nothing to worry about. If they install their signal >> handler at a later time, they have to take care of calling >> xeno_sigwinch_handler and look at its return value. > > Jan, do you agree? The main argument is that people may use third-party > libraries such as, say, libreadline or libqt which intercept the > SIGWINCH signal, and that we do not want to recompile these libraries to > run with Xenomai.
Yes, I'm fine with the current approach + doc + xeno_sigwinch_handler. Jan
Description: OpenPGP digital signature
_______________________________________________ Xenomai-core mailing list Xenomaifirstname.lastname@example.org https://mail.gna.org/listinfo/xenomai-core