atom feed18 messages in org.freebsd.freebsd-threadspatch for threads/76690 - critical - ...
FromSent OnAttachments
Andriy TkachukMar 2, 2005 2:56 pm 
Daniel EischenMar 2, 2005 3:47 pm 
Andriy TkachukMar 3, 2005 6:35 am 
Daniel EischenMar 3, 2005 6:46 am 
David XuMar 3, 2005 6:48 am 
Andriy TkachukMar 3, 2005 6:58 am.patch
Andriy TkachukMar 3, 2005 7:29 am.cc
Andriy TkachukMar 3, 2005 8:07 am 
Andriy TkachukMar 3, 2005 8:10 am 
Andriy TkachukMar 3, 2005 8:15 am 
David XuMar 3, 2005 8:15 am 
Andriy TkachukMar 3, 2005 8:44 am 
Andriy TkachukMar 3, 2005 9:26 am.patch2
David XuMar 3, 2005 10:46 am 
Daniel EischenMar 3, 2005 3:14 pm 
Julian ElischerMar 3, 2005 8:29 pm 
David XuMar 4, 2005 3:24 am 
Andriy TkachukMar 4, 2005 5:57 am 
Subject:patch for threads/76690 - critical - fork hang in child for -lc_r
From:David Xu (davi@freebsd.org)
Date:Mar 4, 2005 3:24:49 am
List:org.freebsd.freebsd-threads

4.x does not have a __malloc_lock symbol exported, I had suggested to add __malloc_lock in FreeBSD 5 libpthread since I saw some broken applications call malloc in child process after fork() and before execv(). :)

Julian Elischer wrote:

the bug is still valid in 4.x

Andriy Tkachuk wrote:

Is there a reason you are still using libc_r?

I don't use it at all, but there was critical bug i threads-pr - so i just decided to fix it since i have had some time )

If this library is needless, why is it still there and this pr in criticals?