> Il giorno 16/mag/2015, alle ore 14:01, Bryan Drewery
> ha scritto:
>
> On 5/16/2015 12:31 PM, Pedro Giffuni wrote:
>> FWIW, and somewhat off-topic ...
>>
>> On 05/16/15 11:40, Bryan Drewery wrote:
>>> ...
>>> Modified:
>>> head/lib/libthr/thread/thr_spec.c
>>>
>>> Thank you for this!
>>>
On 5/16/2015 12:31 PM, Pedro Giffuni wrote:
> FWIW, and somewhat off-topic ...
>
> On 05/16/15 11:40, Bryan Drewery wrote:
>> ...
>> Modified:
>>head/lib/libthr/thread/thr_spec.c
>>
>> Thank you for this!
>>
>> I have a lot of patches at Isilon for adding a libc cleanup function to
>> free all
FWIW, and somewhat off-topic ...
On 05/16/15 11:40, Bryan Drewery wrote:
...
Modified:
head/lib/libthr/thread/thr_spec.c
Thank you for this!
I have a lot of patches at Isilon for adding a libc cleanup function to
free all caching, for use in memory leak detectors such as valgrind. I
even fi
On 5/15/2015 3:40 AM, Konstantin Belousov wrote:
> Author: kib
> Date: Fri May 15 08:40:17 2015
> New Revision: 282948
> URL: https://svnweb.freebsd.org/changeset/base/282948
>
> Log:
> Some third-party malloc(3) implementations use pthread_setspecific(3)
> to handle per-thread information. S
On Friday 15 May 2015 08:40:17 Konstantin Belousov wrote:
> Author: kib
> Date: Fri May 15 08:40:17 2015
> New Revision: 282948
> URL: https://svnweb.freebsd.org/changeset/base/282948
>
> Log:
> Some third-party malloc(3) implementations use pthread_setspecific(3)
> to handle per-thread inform
Author: kib
Date: Fri May 15 08:40:17 2015
New Revision: 282948
URL: https://svnweb.freebsd.org/changeset/base/282948
Log:
Some third-party malloc(3) implementations use pthread_setspecific(3)
to handle per-thread information. Since our pthread_setspecific()
implementation calls calloc(3) t
