On Fri, May 30, 2008 at 3:20 PM, Fabien MAHOT <[EMAIL PROTECTED]> wrote: >> On Thu, May 29, 2008 at 1:26 PM, Fabien MAHOT >> <[EMAIL PROTECTED]> wrote: >>> I succeed to reduce my test program. >>> Now, I ve got two xenomai threads. >>> threadDisplay (prio : 70) : locks a mutex (conflict_lock mutex) and >>> passes >>> between Xenomai and Linux domain. (call to sleep()) >>> threadTimeOut (prio : 80) : Starts one timeout of 5ms and tries to lock >>> the mutex taken by threadDisplay. (Priority Inheritance) >>> >>> threadTimeOut waits the conflict_lock unlock of threadDisplay. With >>> priority inheritance, threadTimeOut gives its priority to threadDisplay. >>> But, threadTimeOut must also do the EndTimeOut() processing. When the >>> timeout end signal arrives, if threadDisplay is into Linux Domain, the >>> system crashes. >> >> Do you have the same crash if you use vanilla Linux timer services >> (__real_timer_create, __real_timer_settime, etc...). >> >> -- >> Gilles > > Hello, > > I try with vanilla linux timer. If threadTimeOut sets up one or two > timeouts, now, it's ok. But if it sets up more than two timeouts, the > system crashes. > I ve got the same error kernel traces as Posix timer use. > > (By the way, In which file vanilla timer services are written ? > __real_timer_create ... are declared in time.h in xenomai files. I look > for in linux and glibc sources but I don t find them.)
Read explanation of the --wrap option in ld documentation. -- Gilles _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
