<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Aug 14, 2015 at 1:55 PM, Saeed Ehteshamifar <span dir="ltr"><<a href="mailto:salpha.2004@gmail.com" target="_blank">salpha.2004@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi, <br> <br></div><span class=""><span><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">There is only a single process so those are not supported at all.</blockquote></span></span><div>Looking
at testsuites/samples/base_sp, I wonder why TA1 terminates by calling
"exit(0)", when "WEXITSTATUS" (and the rest of this family) has not been
implemented.<br>Is parent able to monitor how child terminated via directives other than WEXITSTATUS?<br><br></div></div></blockquote><div>There is no parent, unless you mean in the sense of pthreads. RTEMS is a "single process" environment. Calling exit() eventually leads to halting the system.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>Kind Regards,<br></div>SAeeD<div><div><img src="https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 11, 2015 at 8:06 PM, Joel Sherrill <span dir="ltr"><<a href="mailto:joel.sherrill@oarcorp.com" target="_blank">joel.sherrill@oarcorp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
On 8/11/2015 11:28 AM, Saeed Ehteshamifar wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
Because of different process model, RTEMS doesn't support processes. Therefore many POSIX functions (like fork, exec*) are unimplementable on RTEMS.<br>
Now my question is how to monitor child thread status (if it is correct to use the term "child" in this context) just like what "waitpid" does? Does it make a difference if the thread has been created via classical API or POSIX?<br>
More specifically, I'm interested to directives like WIFEXITED, WEXITSTATUS, WIFSIGNALED, etc.<br>
</blockquote>
<br></span>
There is only a single process so those are not supported at all.<br>
<br>
If a thread crashes with a memory fault, the CPU will generate a trap<br>
and the entire program is halted.<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Kind Regards,<br>
SAeeD<span><font color="#888888"><br>
</font></span></blockquote><span><font color="#888888">
<br>
-- <br>
Joel Sherrill, Ph.D. Director of Research & Development<br>
joel.sherrill@OARcorp.com On-Line Applications Research<br>
Ask me about RTEMS: a free RTOS Huntsville AL 35805<br>
Support Available <a href="tel:%28256%29%20722-9985" value="+12567229985" target="_blank">(256) 722-9985</a><br>
</font></span></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
users mailing list<br>
<a href="mailto:users@rtems.org">users@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br></blockquote></div><br></div></div>