public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: [ANNOUNCEMENT] Uploads for 12 August
Date: Tue, 13 Aug 2013 14:30:00 -0000	[thread overview]
Message-ID: <520A42F0.3080306@cornell.edu> (raw)
In-Reply-To: <520A3EF6.80700@cornell.edu>

On 8/13/2013 10:13 AM, Ken Brown wrote:
> On 8/13/2013 8:08 AM, Angelo Graziosi wrote:
>> Il 13/08/2013 11.52, Angelo Graziosi ha scritto:
>>> Yaakov wrote:
>>>> The following packages (and their subpackages) have been updated for
>>>> both arches:
>>>
>>> After this update my GTK builds of Emacs trunk do not work any more. For
>>> example, the bootstrap of rev. 113816 I did yesterday and that worked
>>> fine up to before this update, now fails so:
>>>
>>> $ emacs -Q &
>>> [1] 3044
>>>
>>> ***MEMORY-ERROR***: [3044]: GSlice: failed to allocate 504 bytes
>>> (alignment: 512): Function not implemented
>>>
>>>
>>> [1]+  Aborted                 (core dumped) emacs -Q
>>>
>>>
>>> So, after this update, I tried a new bootstrap (rev.113838) but id fails
>>> in the same manner:
>>>
>>> if test "no" = "yes"; then \
>>>    rm -f bootstrap-emacs.exe; \
>>>    ln temacs.exe bootstrap-emacs.exe; \
>>> else \
>>>    `/bin/pwd`/temacs --batch --load loadup bootstrap || exit 1; \
>>>    test "X" = X ||  -zex emacs.exe; \
>>>    mv -f emacs.exe bootstrap-emacs.exe; \
>>> fi
>>>
>>> ***MEMORY-ERROR***: [896]: GSlice: failed to allocate 504 bytes
>>> (alignment: 512): Function not implemented
>>>
>>> /bin/sh: line 7:   896 Aborted                 (core dumped)
>>> `/bin/pwd`/temacs --batch --load loadup bootstrap
>>> Makefile:835: recipe for target `bootstrap-emacs.exe' failed
>>> make[2]: *** [bootstrap-emacs.exe] Error 1
>>> make[2]: uscita dalla directory "/work/emacs/Work/src"
>>> Makefile:379: recipe for target `src' failed
>>> make[1]: *** [src] Error 2
>>> make[1]: uscita dalla directory "/work/emacs/Work"
>>> Makefile:1040: recipe for target `bootstrap' failed
>>> make: *** [bootstrap] Error 2
>>> build-emacs.sh: Bootstrap failure...
>>>
>>>
>>> Probably this issue affects also the Cygwin (GTK) package of Emacs..
>>>
>>> It seems that the workaround is to start Emacs with
>>> G_SLICE=always-malloc,
>>>
>>> $ G_SLICE=always-malloc emacs -Q &
>>>
>>>
>>> Ken, wasn't this issue fixed upstream some time ago?
>
> Yes.  The fix was to add the following for the Cygwin build, very early
> in main():
>
>    setenv ("G_SLICE", "always-malloc", 1);
>
> I don't know why this no longer works.  Maybe Glib now does its memory
> management initialization before emacs's main() is entered.
>
> Yaakov, is there any chance that you could patch Glib to do the
> equivalent of G_SLICE=always-malloc on Cygwin?  This isn't really an
> emacs issue.  It would affect any GTK application that provides its own
> malloc rather than using Cygwin's malloc.  (But emacs is probably the
> only such application in the distro.)
>
> An alternative to patching Glib would be to fix the problem directly in
> Cygwin, but I don't know how hard that is and whether Corinna and cgf
> are interested.  The issue, as I understand it, is this: Cygwin allows
> programs to supply their own malloc but not their own memalign.  Glib
> calls memalign, which becomes Cygwin's memalign, which returns ENOSYS
> when Cygwin's malloc is not being used.
>
> There was a long discussion about this on the Cygwin mailing list in
> 2007.  The thread starts at
>
>    http://cygwin.com/ml/cygwin/2007-02/msg00469.html
>
> and continues at
>
>    http://cygwin.com/ml/cygwin/2007-02/msg00503.html
>
> and did not resolve the issue.

While we're waiting for a good solution, I could quickly repackage 
emacs-X11 so that it supplies a wrapper script that sets 
G_SLICE=always-malloc before calling emacs-X11.  If people think that's 
a good idea, I should be able to do it later today.

Ken


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


  reply	other threads:[~2013-08-13 14:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <520A01DF.1040208@alice.it>
2013-08-13 12:08 ` Angelo Graziosi
2013-08-13 14:13   ` Ken Brown
2013-08-13 14:30     ` Ken Brown [this message]
2013-08-13 18:09     ` Yaakov (Cygwin/X)
2013-08-13 18:26       ` Corinna Vinschen
2013-08-13 22:00         ` Ken Brown
2013-08-14  8:10           ` Corinna Vinschen
2013-08-14  9:17             ` Corinna Vinschen
2013-08-14 10:28               ` Ken Brown
2013-08-14 10:53                 ` Corinna Vinschen
2013-08-14 11:34                   ` Corinna Vinschen
2013-08-14 11:59                     ` Corinna Vinschen
2013-08-14 12:14                       ` Ken Brown
2013-08-14 15:55                         ` Ken Brown
2013-08-14 19:00                           ` Corinna Vinschen
2013-08-14 12:28                       ` Ryan Johnson
2013-08-14 14:05                         ` Corinna Vinschen
2013-08-14 14:55                           ` Corinna Vinschen
2013-08-13 19:26       ` Charles Wilson
2013-08-13 14:46   ` Angelo Graziosi
2013-08-14 19:59     ` Angelo Graziosi
2013-08-12 19:38 Yaakov (Cygwin/X)
2013-08-24  0:30 ` Enrico Forestieri

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=520A42F0.3080306@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-xfree@cygwin.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.
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).