From owner-freebsd-stable Fri Apr 27 3:25:59 2001 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [202.53.40.210]) by hub.freebsd.org (Postfix) with ESMTP id B10BC37B422 for ; Fri, 27 Apr 2001 03:25:52 -0700 (PDT) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id UAA80917; Fri, 27 Apr 2001 20:24:27 +1000 (EST) (envelope-from gnb@itga.com.au) Received: from itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id UAA18292; Fri, 27 Apr 2001 20:24:26 +1000 (EST) Message-Id: <200104271024.UAA18292@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Doug Hardie Cc: stable@FreeBSD.ORG, Kris Kennaway Subject: Re: Illegal Instruction in libm - Problem solved.... In-reply-to: Your message of Thu, 26 Apr 2001 23:20:17 -0700. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Apr 2001 20:24:26 +1000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > There is an interesting difference in malloc. It defines the symbol > free and if you use that symbol in your program then it tends to > write over some part of your program. By changing the symbol in my > program (an int) to a different name, the problem goes away and it > works properly. I believe this behavior is new because it didn't > have this problem in FreeBSD 4.2-RELEASE. Free() has been part of the malloc() package for as long as the C language has existed (more or less). Redefining standard library names in your code is and always has been a bug. The difference might be that under 4.2 the bug has repeatable consequences due to different code layout in the library or whatever. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message