From owner-freebsd-bugs Wed Apr 5 21:10:10 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EB66537B95F for ; Wed, 5 Apr 2000 21:10:08 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id VAA13196; Wed, 5 Apr 2000 21:10:03 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 5 Apr 2000 21:10:03 -0700 (PDT) Message-Id: <200004060410.VAA13196@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Lachlan O'Dea" Subject: Re: bin/16924: tmpfile(3) ignores TMPDIR and always uses /tmp Reply-To: "Lachlan O'Dea" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/16924; it has been noted by GNATS. From: "Lachlan O'Dea" To: Daniel Hagan Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/16924: tmpfile(3) ignores TMPDIR and always uses /tmp Date: Thu, 6 Apr 2000 14:03:55 +1000 On Wed, Apr 05, 2000 at 09:54:37PM -0400, Daniel Hagan wrote: > You need to do error checking on your calls to malloc. Other than that, I > think it looks ok on an initial reading. (I'm certainly not an expert on > libc though.) Thanks for looking at this. I wanted to include error checking, but I wasn't sure of what action to take if an error occurred. I remember finding some other malloc calls in libc that didn't check for errors, so I just left it alone. If anyone can point me to an example of how to handle this, I'd appreciate it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message