From owner-freebsd-current Sun Sep 20 07:00:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28767 for freebsd-current-outgoing; Sun, 20 Sep 1998 07:00:58 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28740 for ; Sun, 20 Sep 1998 07:00:52 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id OAA28537 for ; Sun, 20 Sep 1998 14:01:06 GMT Date: Sun, 20 Sep 1998 15:01:06 +0100 (BST) From: Doug Rabson To: current@FreeBSD.ORG Subject: vfork and malloc Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it safe to call malloc in the child process after a vfork? I have been trying to debug a rare fault in make which goes away when I change the vfork() in src/usr.bin/make/compat.c to fork(). After the vfork, it calls execvp() which allocates memory via strdup(). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891 Fax: +44 181 381 1039 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message