> 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 [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
