From owner-freebsd-hackers Thu Mar 23 23:44:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DD6BD37B56D for ; Thu, 23 Mar 2000 23:44:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA09084; Thu, 23 Mar 2000 23:44:14 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Mar 2000 23:44:14 -0800 (PST) From: Matthew Dillon Message-Id: <200003240744.XAA09084@apollo.backplane.com> To: Chad David Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :In the case of malloc(), wmesg is set to type->ks_shortdesc, which is :not part of the current functions stack, so it is safe for malloc :to return. Unless I am wrong, "string", is an automatic variable, and :when the current function returns it is no longer vaild. : :With tsleep() this would never be a problem as tsleep() blocks. : :Chad No. "string" is a 'const char *' -- it is global read-only data. It is most certainly not an automatic function variable. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message