From: Eli Zaretskii <eliz@gnu.org>
Cc: jbuehler@spirentcom.com, emacs-devel@gnu.org
Subject: Re: Failures in build Emacs-CVS on Cygwin
Date: Sat, 25 Nov 2006 13:06:26 +0200 [thread overview]
Message-ID: <uk61j6b0t.fsf@gnu.org> (raw)
In-Reply-To: <Pine.OSF.4.21.0611251043340.13657-100000@ax0rm1.roma1.infn.it> (message from Angelo Graziosi on Sat, 25 Nov 2006 10:52:42 +0100 (MET))
> Date: Sat, 25 Nov 2006 10:52:42 +0100 (MET)
> From: Angelo Graziosi <Angelo.Graziosi@roma1.infn.it>
> cc: emacs-devel@gnu.org, jbuehler@spirentcom.com
>
> relinquish
> /tmp/emacs/src/ralloc.c:338
> r_alloc_sbrk
> /tmp/emacs/src/ralloc.c:934
> _malloc_internal
> /tmp/emacs/src/gmalloc.c:504
> emacs_blocked_malloc
> /tmp/emacs/src/alloc.c:1244
Looks like some problem with memory allocation. Several similar
crashes of the Cygwin port were reported during the last months, IIRC.
prev parent reply other threads:[~2006-11-25 11:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 1:22 Building Emacs-cvs on Cygwin (GCC summary) Maks Romih
2006-10-30 19:16 ` Richard Stallman
2006-10-30 20:31 ` Eric Hanchrow
2006-10-30 21:05 ` Eli Zaretskii
2006-10-30 21:26 ` Eric Hanchrow
2006-10-30 21:44 ` Jason Rumney
2006-11-05 10:52 ` Jari Aalto
2006-11-05 11:55 ` Eli Zaretskii
2006-10-30 21:06 ` Eli Zaretskii
2006-11-04 12:12 ` Eli Zaretskii
2006-11-21 1:28 ` 22.1 Cygwin emacs timeframe query Angelo Graziosi
2006-11-21 1:46 ` Angelo Graziosi
2006-11-21 9:35 ` Angelo Graziosi
2006-11-22 14:49 ` Failures in build Emacs-CVS on Cygwin Angelo Graziosi
2006-11-22 22:23 ` Eli Zaretskii
2006-11-23 0:07 ` Angelo Graziosi
2006-11-23 4:15 ` Eli Zaretskii
2006-11-23 14:04 ` Angelo Graziosi
2006-11-23 23:55 ` Angelo Graziosi
2006-11-24 21:17 ` Eli Zaretskii
2006-11-24 23:32 ` Angelo Graziosi
2006-11-25 11:07 ` Eli Zaretskii
2006-11-25 9:52 ` Angelo Graziosi
2006-11-25 11:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uk61j6b0t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jbuehler@spirentcom.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.