From owner-freebsd-bugs Sun Apr 21 11:10: 5 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id D485737B417 for ; Sun, 21 Apr 2002 11:10:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g3LIA2U26362; Sun, 21 Apr 2002 11:10:02 -0700 (PDT) (envelope-from gnats) Date: Sun, 21 Apr 2002 11:10:02 -0700 (PDT) Message-Id: <200204211810.g3LIA2U26362@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Malone Subject: Re: kern/37178: rfork results the core dump with RFMEM flag. Reply-To: David Malone Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/37178; it has been noted by GNATS. From: David Malone To: Artem Zagorulko Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/37178: rfork results the core dump with RFMEM flag. Date: Sun, 21 Apr 2002 19:07:02 +0100 On Wed, Apr 17, 2002 at 01:34:22AM -0700, Artem Zagorulko wrote: > rfork results the core dump with RFMEM flag when I use kill function after child creating to signal to child. I believe that you need magic glue to get rfork to create lightweight threads - as the man page says "thus rfork() with the RFMEM flag may not generally be called directly from high level languages including C". David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message