From owner-freebsd-hackers Thu Mar 23 23:50:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lodge.guild.ab.ca (lodge.guild.ab.ca [209.91.118.66]) by hub.freebsd.org (Postfix) with ESMTP id BDBAE37C08A for ; Thu, 23 Mar 2000 23:50:44 -0800 (PST) (envelope-from davidc@acns.ab.ca) Received: from localhost (davidc@localhost) by lodge.guild.ab.ca (8.9.3/8.9.3) with ESMTP id AAA13132; Fri, 24 Mar 2000 00:57:59 -0700 (MST) (envelope-from davidc@acns.ab.ca) Date: Fri, 24 Mar 2000 00:57:59 -0700 (MST) From: Chad David X-Sender: davidc@lodge.guild.ab.ca To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: vm_await() In-Reply-To: <200003240744.XAA09084@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After thinking about it, I don't know what I was thinking :(. Sorry for wasting you time. Chad On Thu, 23 Mar 2000, Matthew Dillon wrote: > > : > :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