From owner-freebsd-bugs  Wed Mar 12 12:10:10 1997
Return-Path: <owner-bugs>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA08564
          for bugs-outgoing; Wed, 12 Mar 1997 12:10:10 -0800 (PST)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA08550;
          Wed, 12 Mar 1997 12:10:05 -0800 (PST)
Date: Wed, 12 Mar 1997 12:10:05 -0800 (PST)
Message-Id: <199703122010.MAA08550@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: Poul-Henning Kamp <phk@critter.dk.tfs.com>
Subject: Re: kern/2964: malloc() returns non-null when it should not 
Reply-To: Poul-Henning Kamp <phk@critter.dk.tfs.com>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/2964; it has been noted by GNATS.

From: Poul-Henning Kamp <phk@critter.dk.tfs.com>
To: jmaslak@blackfire.com
Cc: FreeBSD-gnats-submit@FreeBSD.ORG
Subject: Re: kern/2964: malloc() returns non-null when it should not 
Date: Wed, 12 Mar 1997 21:08:23 +0100

 >	I'm assuming this is a kernel problem, although it may be a gnu
 >	problem.
 >
 >	If malloc is called as follows:
 >		malloc((size_t) 0xffffffff)
 >	it returns a non-null pointer.
 
 This is a sign extension problem in malloc() which I have not gotten
 around to fix properly.  It's on my "known but mostly harmless" list.
 
 malloc isn't a kernel function btw, it lives in libc.
 
 --
 Poul-Henning Kamp           | phk@FreeBSD.ORG       FreeBSD Core-team.
 http://www.freebsd.org/~phk | phk@login.dknet.dk    Private mailbox.
 whois: [PHK]                | phk@tfs.com           TRW Financial Systems, Inc.
 Power and ignorance is a disgusting cocktail.