all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: LENNART BORGMAN <lennart.borgman.073@student.lu.se>,
	Romain Francoise <romain@orebokech.com>,
	emacs-devel@gnu.org
Subject: Re: mem leak
Date: Mon, 24 Apr 2006 23:44:37 +0900	[thread overview]
Message-ID: <87psj72fu2.fsf@catnip.gol.com> (raw)
In-Reply-To: <jwvu08jgo13.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 24 Apr 2006 08:24:59 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Overflow can happen because the .elc file is missing, and the
> not-completely-functional Emacs that results is quite functional enough to
> then byte-compile the file, so it makes bootstrapping easier.

Hmmm, how hard would it be to have it runnable, but not _installable_ in
such a case (for instance, if it retained the executable, but gave it
another name, "emacs-non-pure" or something)?

[I don't know whether it's easy to get the results of the failure in a
form that make can easily use...]

-Miles

-- 
Somebody has to do something, and it's just incredibly pathetic that it
has to be us.  -- Jerry Garcia

  reply	other threads:[~2006-04-24 14:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-24  7:33 mem leak LENNART BORGMAN
2006-04-24  8:01 ` Miles Bader
2006-04-24  8:18   ` Romain Francoise
2006-04-24  8:26     ` Miles Bader
2006-04-24  8:39       ` Miles Bader
2006-04-24 12:24         ` Stefan Monnier
2006-04-24 14:44           ` Miles Bader [this message]
2006-04-24 17:52         ` Richard Stallman
2006-04-26 13:44           ` memory consumption with pure-space-overflow (was: mem leak) Reiner Steib
2006-04-27  4:36             ` Richard Stallman
2006-04-27 13:52               ` memory consumption with pure-space-overflow Reiner Steib
2006-04-27 21:27                 ` Richard Stallman
2006-05-02 14:07                   ` Reiner Steib
2006-05-05 12:50                   ` Eli Zaretskii
2006-05-05 14:10                     ` Reiner Steib
2006-05-05 22:14                       ` Richard Stallman
2006-05-06 11:42                         ` Reiner Steib
2006-05-06 23:36                           ` Richard Stallman
2006-05-09 20:44                           ` Juri Linkov
2006-05-11  3:44                             ` Richard Stallman
2006-05-11 23:01                               ` Undocumented %-constructs (was: memory consumption with pure-space-overflow) Juri Linkov
2006-05-12  1:44                                 ` Undocumented %-constructs Johan Bockgård
2006-05-12 11:14                                   ` Juri Linkov
2006-05-14 23:29                                 ` Undocumented %-constructs (was: memory consumption with pure-space-overflow) Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2006-04-24  3:31 mem leak Miles Bader
2006-04-24  3:37 ` David Kastrup
2006-04-24  4:15   ` Miles Bader

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=87psj72fu2.fsf@catnip.gol.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    --cc=romain@orebokech.com \
    /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.