Monitor thread execution (replacement for waitpid)

[Gedare Bloom]

On Fri, Aug 14, 2015 at 1:55 PM, Saeed Ehteshamifar <salpha.2004 at gmail.com>
wrote:

> Hi,
>
>
>> There is only a single process so those are not supported at all.
>
> 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.
> Is parent able to monitor how child terminated via directives other than
> WEXITSTATUS?
>
> 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.


> Kind Regards,
> SAeeD
>
> On Tue, Aug 11, 2015 at 8:06 PM, Joel Sherrill <joel.sherrill at oarcorp.com>
> wrote:
>
>>
>>
>> On 8/11/2015 11:28 AM, Saeed Ehteshamifar wrote:
>>
>>> Hi,
>>>
>>> Because of different process model, RTEMS doesn't support processes.
>>> Therefore many POSIX functions (like fork, exec*) are unimplementable on
>>> RTEMS.
>>> 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?
>>> More specifically, I'm interested to directives like WIFEXITED,
>>> WEXITSTATUS, WIFSIGNALED, etc.
>>>
>>
>> There is only a single process so those are not supported at all.
>>
>> If a thread crashes with a memory fault, the CPU will generate a trap
>> and the entire program is halted.
>>
>>
>>
>>> Kind Regards,
>>> SAeeD
>>>
>>
>> --
>> Joel Sherrill, Ph.D.             Director of Research & Development
>> joel.sherrill at OARcorp.com        On-Line Applications Research
>> Ask me about RTEMS: a free RTOS  Huntsville AL 35805
>> Support Available                (256) 722-9985
>>
>
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20150816/6d15e739/attachment-0002.html>