ports/69347: xemacs spews many "past acceptable memory limits" warning messages

Andrew Heybey ath at niksun.com
Tue Jul 20 16:30:27 UTC 2004

>Number:         69347
>Category:       ports
>Synopsis:       xemacs spews many "past acceptable memory limits" warning messages
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 20 16:30:26 GMT 2004
>Originator:     Andrew Heybey
>Release:        FreeBSD 4.9-RELEASE-p5 i386
Niksun, Inc.
System: FreeBSD stiegl.mj.niksun.com 4.9-RELEASE-p5 FreeBSD 4.9-RELEASE-p5 #0: Tue Apr 20 22:35:25 EDT 2004 ath at stiegl.mj.niksun.com:/scratch/obj/x/src/sys/STIEGL i386

Ports tree cvsup'ed sometime last week.


The port patches src/mem-limits.h to declare the "lim_data" variable
as rlim_t (a 64-bit type), but src/emacs.c still defines it as an
integer.  This makes the memory limit checking think that there are
zero bytes available.


Install the editors/xemacs port.  Run xemacs.  See the warning messages.


Put this diff in files/patch-emacs.c of the port.

--- src/emacs.c.orig	Wed Jan 15 07:18:00 2003
+++ src/emacs.c	Tue Jul 20 12:02:41 2004
@@ -344,7 +344,7 @@
 /* Number of bytes of writable memory we can expect to be able to get */
-unsigned int lim_data;
+rlim_t lim_data;


More information about the freebsd-ports-bugs mailing list