Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 3 Jul 2019 07:31:56 +0000
From: "Poggiali, Antonio" <>
To: "" <>
Subject: Re: pthread_getname_np implementation

On Fri, 21 Jun 2019 14:18:38 -0400, Rich Felker wrote:
> So the situation is nasty, but not as bad as I remember. The
> conflicting definitions are basically junk (unusable) or minor
> gratuitous differences (int vs size_t). However this does suggest that
> there's a decent motivation for discouraging the proliferation of its
> use in applications.

> Thoughts?

I think if you provide a way to set a name,  there should be a way to get it as well.
The majority of the systems lacks the API or have it as glibc does so why not implement it glibc style?


CONFIDENTIALITY NOTICE. This message is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please destroy all copies of the original message, including any and all attachments, and notify the sender immediately.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.