Date: Mon, 24 Oct 2005 10:19:39 -0700 From: "Farid Bavandpouri" <fbavandpouri@amcc.com> To: <freebsd-threads@freebsd.org> Subject: RE: threads/76690: fork hang in child for (-lc_r & -lthr) Message-ID: <9D1E2BDCB5C57B46B56E6D80843439EBBB87ED@SDCEXCHANGE01.ad.amcc.com>
index | next in thread | raw e-mail
Remove/unsubscribe mmontaseri@amcc.com -----Original Message----- From: owner-freebsd-threads@freebsd.org [mailto:owner-freebsd-threads@freebsd.org] On Behalf Of Marc Olzheim Sent: Monday, October 24, 2005 9:59 AM To: Daniel Eischen Cc: Marc Olzheim; freebsd-threads@freebsd.org; Marc Olzheim; David Xu; Sven Berkvens-Matthijsse Subject: Re: threads/76690: fork hang in child for (-lc_r & -lthr) On Mon, Oct 24, 2005 at 12:41:01PM -0400, Daniel Eischen wrote: > > But then the free() in the child process may be using an unstable > > state of the malloc system (because if you don't acquire the lock > > before the fork(), malloc() may be busy in the middle of the fork()). > > I don't think that can happen because libc_r will not switch out a > thread that is in a critical region (and libc locks are critical > regions) until it leaves the region. Well, that would be the idea, but GDB traces prove otherwise... :P And that's why the patch prevents the test program in the PR from hanging. Marc -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. All unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9D1E2BDCB5C57B46B56E6D80843439EBBB87ED>