From owner-freebsd-stable Tue Aug 20 15:27:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0227C37B400 for ; Tue, 20 Aug 2002 15:27:31 -0700 (PDT) Received: from cerberus.apdata.com.au (cerberus.apdata.com.au [202.14.95.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30D5E43E4A for ; Tue, 20 Aug 2002 15:27:30 -0700 (PDT) (envelope-from ian@niw.com.au) Received: from localhost (localhost [127.0.0.1]) by cerberus.apdata.com.au (Postfix) with SMTP id 3B57243D3E for ; Wed, 21 Aug 2002 07:57:29 +0930 (CST) Received: from axiom.niw.com.au (unknown [192.168.213.1]) by cerberus.apdata.com.au (Postfix) with ESMTP id DABAF43D3A for ; Wed, 21 Aug 2002 07:57:28 +0930 (CST) Received: from localhost (localhost [127.0.0.1]) by axiom.niw.com.au (Postfix) with ESMTP id 3979035EC6 for ; Wed, 21 Aug 2002 07:57:28 +0930 (CST) Received: by axiom.niw.com.au (Postfix, from userid 1000) id A4C5135EB2; Wed, 21 Aug 2002 07:57:27 +0930 (CST) Date: Wed, 21 Aug 2002 07:57:27 +0930 From: Ian West To: freebsd-stable@freebsd.org Subject: Malloc backwards compat problem in stable as of yesterday ? Message-ID: <20020820222727.GC407@axiom.niw.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Virus-Scanned: by AMaViS perl-10 X-Virus-Scanned: by kavpostfix Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The following program when compiled on a box cvs updated to RELENG_4 late yesterday (about 8 hours ago) works fine on the box itself, but the dynamic binary fails (returns 0) when run on a box running RELENG_4 from about a week ago. Is this a known and expected issue ? #include #include int main(int argc, char **argv){ char *temp=(char *)malloc(24); printf("temp=%p\n",temp); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message