all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: James Van Artsdalen <james@jrv.org>
Subject: lim_data too narrow
Date: Wed, 17 Dec 2003 18:58:55 -0600 (CST)	[thread overview]
Message-ID: <200312180058.hBI0wtaq054209@bigtex.jrv.org> (raw)

This bug report will be sent to the Free Software Foundation,
 not to your local site managers!!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.

In GNU Emacs 21.3 (amd64--freebsd)

lim_data is too narrow to hold the size of the process data segment.
On my system (with 8 GB of RAM) the rlimit is by default (in KB):

$ ulimit -d
8388608

lim_data needs to be at least as wide as the rlimit .rlim_cur field or
truncation occurs.

I'm not sure what the right cross-platform portable way to detect this
situation is.  The patch below is an example.

Note that this change is not sufficient to build emacs for amd64.

*** mem-limits.h.~1~    Wed Mar  8 12:49:46 2000
--- mem-limits.h        Wed Dec 17 03:15:24 2003
***************
*** 98,104 ****
  static POINTER data_space_start;
  
  /* Number of bytes of writable memory we can expect to be able to get */
! static unsigned long lim_data;
  
  #ifdef NO_LIM_DATA
  static void
--- 98,104 ----
  static POINTER data_space_start;
  
  /* Number of bytes of writable memory we can expect to be able to get */
! static rlim_t lim_data;
  
  #ifdef NO_LIM_DATA
  static void

             reply	other threads:[~2003-12-18  0:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18  0:58 James Van Artsdalen [this message]
2003-12-22  4:07 ` lim_data too narrow Richard Stallman
2003-12-22  6:17   ` Eli Zaretskii
2003-12-23  5:03     ` Richard Stallman
2004-01-04 19:53     ` Stefan Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200312180058.hBI0wtaq054209@bigtex.jrv.org \
    --to=james@jrv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.