On 16/01/17 12:56, Chris Johns wrote:
Who looks at the RTEMS documentation to figure out what a POSIX function
>does? I never used the POSIX API manual.
>
Many people do. It is important when something is not working as
expected. Not all users are keen to jump into the RTEMS source code to
fig
On 16/1/17 7:19 pm, Sebastian Huber wrote:
>
>
> On 16/01/17 09:08, Chris Johns wrote:
>> On 16/1/17 5:52 pm, Sebastian Huber wrote:
>>> On 13/01/17 18:59, Gedare Bloom wrote:
On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber
wrote:
> Hello,
>
> I added optional user-defined
On 16/01/17 09:08, Chris Johns wrote:
On 16/1/17 5:52 pm, Sebastian Huber wrote:
On 13/01/17 18:59, Gedare Bloom wrote:
On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber
wrote:
Hello,
I added optional user-defined thread names.
https://devel.rtems.org/ticket/2858
The GNU pthread extension
On 16/1/17 5:52 pm, Sebastian Huber wrote:
> On 13/01/17 18:59, Gedare Bloom wrote:
>> On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber
>> wrote:
>>> Hello,
>>>
>>> I added optional user-defined thread names.
>>>
>>> https://devel.rtems.org/ticket/2858
>>>
>>> The GNU pthread extensions pthread_ge
On 13/01/17 18:59, Gedare Bloom wrote:
On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber
wrote:
Hello,
I added optional user-defined thread names.
https://devel.rtems.org/ticket/2858
The GNU pthread extensions pthread_getname_np() and pthread_setname_np() are
now available in RTEMS and work
On Fri, Jan 13, 2017 at 3:25 AM, Sebastian Huber
wrote:
> Hello,
>
> I added optional user-defined thread names.
>
> https://devel.rtems.org/ticket/2858
>
> The GNU pthread extensions pthread_getname_np() and pthread_setname_np() are
> now available in RTEMS and work for all threads (internal, Cla
Hello,
I added optional user-defined thread names.
https://devel.rtems.org/ticket/2858
The GNU pthread extensions pthread_getname_np() and pthread_setname_np()
are now available in RTEMS and work for all threads (internal, Classic,
POSIX, FreeBSD).
http://man7.org/linux/man-pages/man3/pthre
