unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Aidan Kehoe <kehoea@parhasard.net>
Cc: emacs-devel@gnu.org
Subject: Re: Possible memory corruption problem
Date: Tue, 14 Feb 2006 10:29:16 +0100	[thread overview]
Message-ID: <17393.41708.76191.538450@parhasard.net> (raw)
In-Reply-To: <m2fymml6f6.fsf@ordesa.lan>


 Ar an ceathrú lá déag de mí Feabhra, scríobh Piet van Oostrum: 

 > >>> Emacs tries to estimate how much memory is available, but that estimate
 > >>> may not really work.  For instance, it never works for me.
 > >>> The code to estimate available space worked in the 80s on Unix,
 > >>> but it may need adaptation to the systems of today.

Ben Wing implemented this in XEmacs by looking at what getrlimit(2) returns,
which is effective and consistent with what modern OSes do. He also
abstracted it to fall back to ulimit if that’s not available, or to use the
Win32-specific procedure when that’s appropriate. 

 > >EZ> It's possible that the existing estimate doesn't work on systems that
 > >EZ> don't use sbrk.  I believe GNU/Linux is one of those systems.
 > 
 > It seems it is not used on Mac OS X either. The man page says:
 >      The brk and sbrk functions are historical curiosities left over from
 >      ear- lier days before the advent of virtual memory management.
 > 
 > And I run a test program with malloc calls, set a breakpoint at brk and
 > sbrk and it did not reach those.

Which is well and good; implementing a heap using mmap, for example, means
you can release memory back to the OS once it’s been freed. 

-- 
I AM IN JAIL AND ALLOWED SEND ONLY ONE CABLE SINCE WAS ARRESTED WHILE
MEASURING FIFTEEN FOOT WALL OUTSIDE PALACE AND HAVE JUST FINISHED COUNTING
THIRTY EIGHT THOUSAND FIVE HUNDERED TWENTY TWO NAMES WHOS WHO IN MIDEAST.

  reply	other threads:[~2006-02-14  9:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 15:36 Possible memory corruption problem Piet van Oostrum
2006-02-06 19:13 ` Eli Zaretskii
2006-02-06 22:14   ` Piet van Oostrum
2006-02-13  4:40   ` Richard M. Stallman
2006-02-14  4:35     ` Eli Zaretskii
2006-02-14  7:56       ` Piet van Oostrum
2006-02-14  9:29         ` Aidan Kehoe [this message]
2006-02-15  4:39           ` Richard M. Stallman
2006-02-16 13:21             ` Piet van Oostrum
2006-02-20 18:42               ` Richard M. Stallman
2006-02-14 22:17       ` Richard M. Stallman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=17393.41708.76191.538450@parhasard.net \
    --to=kehoea@parhasard.net \
    --cc=emacs-devel@gnu.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).