Hi Murillo,
if your system crashes, you should load the rtl-debug modul prior starting
your own stuff. Even if you don not use the debugger, it prevents system
crashes in most cases, because it handles the exceptions from rtl.
Where do you create your threads ?
a.) in the init_module()
b.) from an fifo - handler created in init_module()
c.) from a running rtl - thread
I found out that you have to obay various things like pthread_detach() etc.
in order to prevent rtl to mess up the system stack when a thread finishes.
If you explain more, we can see if your problem might be caused by these
effects.
- Andreas Motzkus -
inmess GmbH
Borngasse 9 Voice: +49 6152 9779-11
Fax : +49 6152 9779-20
D - 64572 Buettelborn Email : [EMAIL PROTECTED]
On Tuesday 16 July 2002 15:59, you wrote:
> Hi there
> I apologise if this question has already been posted but I'm new in this
> list.
> I have an application that supports multiple real-time threads that run at
> rates specified by the user. If these rates are very large the computer
> crashes. My hypothesis is that a thread is invoked before it is finished
> since the execution time is larger that the thread period. Is there any
> mechanism to prevent this from happening. I tried with a watchdog thread
> with the highest priority but it didn't seem to work.
> many thanks in advance
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
--
For more information on Real-Time Linux see:
http://www.rtlinux.org/
