From owner-freebsd-current Fri Nov 22 7:25:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D94937B401 for ; Fri, 22 Nov 2002 07:25:24 -0800 (PST) Received: from popelschnipser.de (ultrakoreggd.org [217.160.78.206]) by mx1.FreeBSD.org (Postfix) with SMTP id 8DC8A43EB3 for ; Fri, 22 Nov 2002 07:25:23 -0800 (PST) (envelope-from marc@informatik.uni-bremen.de) Received: (qmail 19986 invoked by uid 1048); 22 Nov 2002 15:25:22 -0000 Received: from marc@informatik.uni-bremen.de by p10089345 by uid 1045 with qmail-scanner-1.15 (clamscan: 0.54. spamassassin: 2.42. Clear:. Processed in 0.272116 secs); 22 Nov 2002 15:25:22 -0000 Received: from unknown (HELO ?192.168.100.100?) (217.82.114.46) by ultrakoreggd.org with SMTP; 22 Nov 2002 15:25:22 -0000 Date: Fri, 22 Nov 2002 16:25:20 +0100 From: Marc Recht To: freebsd-current@FreeBSD.ORG Subject: malloc(0) broken? Message-ID: <79620000.1037978720@leeloo.intern.geht.de> X-Mailer: Mulberry/3.0.0a5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! A malloc(0) returns always 0x800 on my system. This causes some third-party software to fail, because they expect malloc(0) to return NULL. Is this a bug or a feature? malloc(3) doesn't mention anything. Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message