Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 9 Jul 2019 14:19:26 -0400
From: Rich Felker <>
To: "Poggiali, Antonio" <>
Cc: "" <>
Subject: Re: Re: pthread_getname_np implementation

On Wed, Jul 03, 2019 at 07:31:56AM +0000, Poggiali, Antonio wrote:
> 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?

Based on the previous discussion of this and others' comments, I think
adding it is probably the right thing to do. I'll look at it after
rolling the release. Ping the list again if I don't get around to it


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.