Hi! > I think that instead of an addition of "the common syscall preparation" to a > define, > it would be better to implement a wrapper to the rt_sigaction syscall. > > Like this one. > > Its basis is a combination of glibc implementations of sigaction() for > different > platforms. But it also accepts '-1' for act, oact to check EFAULT errno code > (glibc implementation doesn't handle such a situtation). > > How do you think where the best place is to put this wrapper implementation?
Given that the testcases are statically linked with the test library anyway the easiest solution would be include/lapi/rt_sigaction.h. -- Cyril Hrubis chru...@suse.cz ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ Ltp-list mailing list Ltp-list@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ltp-list
