From: Paul Eggert <eggert@cs.ucla.edu>
To: Jim Meyering <jim@meyering.net>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: please set both MALLOC_PERTURB_ and MALLOC_CHECK_ envvars
Date: Sat, 28 May 2011 22:44:11 -0700 [thread overview]
Message-ID: <4DE1DD2B.5020902@cs.ucla.edu> (raw)
In-Reply-To: <874o4fx17z.fsf@rho.meyering.net>
On 05/27/11 14:50, Jim Meyering wrote:
> export MALLOC_PERTURB_=$((RANDOM % 255 + 1))
> export MALLOC_CHECK_=3
>
I tried that, on Fedora 14 x86-64, and the Emacs trunk build failed
as follows:
Compiling language/thai-word.el
In toplevel form:
language/thai-word.el:10738:5:Error: Memory exhausted--use C-x s then exit and restart Emacs
make[2]: *** [language/thai-word.elc] Error 1
make[2]: Leaving directory `/home/eggert/src/gnu/emacs/int-hash/lisp'
As near as I can discover, Emacs was fine, but the malloc debugging
caused it to use so much more memory that Emacs ran out of memory
trying to compile thai-word.el. This is on a host with
8 GiB of RAM.
Perhaps there is a real Emacs bug in there somewhere, but I spent
a reasonable amount of time looking for it unsuccessfully.
next prev parent reply other threads:[~2011-05-29 5:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 21:50 please set both MALLOC_PERTURB_ and MALLOC_CHECK_ envvars Jim Meyering
2011-05-27 21:57 ` Jim Meyering
2011-05-28 0:13 ` Thien-Thi Nguyen
2011-05-28 18:52 ` Jim Meyering
2011-05-30 10:30 ` Jim Meyering
2011-05-30 17:49 ` Andreas Schwab
2011-05-28 20:19 ` Chong Yidong
2011-05-28 20:33 ` Jim Meyering
2011-05-29 5:44 ` Paul Eggert [this message]
2011-05-29 7:32 ` Jim Meyering
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=4DE1DD2B.5020902@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
/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).