From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Any success with emacs 2.1.4 under cygwin 1.5.21?
Date: Sat, 30 Sep 2006 11:32:15 +0300 [thread overview]
Message-ID: <uac4hrbzk.fsf@gnu.org> (raw)
In-Reply-To: <451C4380.7040800@pobox.com> (spaus@pobox.com)
> Date: Thu, 28 Sep 2006 17:49:52 -0400
> From: "Sean M. Paus" <spaus@pobox.com>
>
> I've recently upgraded my cygwin installation to 1.5.21. Since then, I
> have had no luck getting emacs to run. I've tried the stock 21.2 that
> comes with the cygwin distribution, the test 21.3 that was posted a
> while back, and I've even downloaded and (well half) built the latest
> sources from the emacs CVS repository.
>
> The problem is that emacs just hangs and takes up gobs of CPU. I
> ultimately tracked this down to a tight infinite loop in
> _malloc_internal (gmalloc.c). For some reason, align (also in
> gmalloc.c) is returning a pointer that is smaller than _heapbase. The
> calculation to determine what block the newly requested memory is in
> (BLOCK(result+size)) returns a ridiculously huge number. Since
> _malloc_internal incrementally doubles the new size of the heap until
> the requested memory fits, at some point the multiplication overflows
> and newsize gets a value of 0. Since 0 * 2 is always zero, the test for
> BLOCK(result+size) > newsize will always succeed and _malloc_internal
> gets stuck in a tight loop multiplying 0 by 2 forever.
Thanks for investigating the problem, but this is not a good place to
post such reports. Please use emacs-devel@gnu.org, since the problem
seems to exist in the CVS code as well (or did I misunderstand?).
Also, you may wish to search the archives of emacs-devel and
emacs-pretest-bug mailing lists, as I think something similar was
reported in the past.
(I myself don't use Cygwin, so I cannot help you more at this time.)
prev parent reply other threads:[~2006-09-30 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-28 21:49 Any success with emacs 2.1.4 under cygwin 1.5.21? Sean M. Paus
2006-09-30 8:32 ` Eli Zaretskii [this message]
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=uac4hrbzk.fsf@gnu.org \
--to=eliz@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.
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).