Date: Wed, 12 Apr 1995 08:20:16 -0700 From: Ed Hudson <elh@p5.spnet.com> To: hackers@FreeBSD.org Cc: elh@p5.spnet.com Message-ID: <199504121520.IAA07172@p5.spnet.com>
next in thread | raw e-mail | index | archive | help
howdy. while you folks are reconsidering malloc... a while ago i encountered an 'application almost bug' wherein sbrk(1) returns (old_mem+1). Some other unix's (e.g., SunOS) return a double word aliged value. since SunOS is perhaps one of the largest porting sources that FreeBSD can get applications from, i think that obscure bugs, as well as obscure performance anomalies could be prevented if FreeBSD were to adopt this behavior. i'd like to ask you folks to reconsider adopting the SunOS sbrk() behavior... in the interests of maximizing the acceptance of FreeBSD by minimizing the porting hassles, as well as performance problems for random applications that do their own sbrk'ing (and not malloc-ing). and yes, there probably aren't many applications that do this, but i think the current sbrk() behavior is a tiny time bomb. thanks, -elh
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504121520.IAA07172>