public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-xfree@cygwin.com
Subject: Re: [ANNOUNCEMENT] Uploads for 12 August
Date: Tue, 13 Aug 2013 18:26:00 -0000 [thread overview]
Message-ID: <20130813182653.GA4315@calimero.vinschen.de> (raw)
In-Reply-To: <520A7654.3080207@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 1976 bytes --]
On Aug 13 13:09, Yaakov (Cygwin/X) wrote:
> On 2013-08-13 09:13, Ken Brown wrote:
> >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.
>
> Exactly; in glib-2.36, g_type_init has been moved to a ctor, which
> is automatically called before main(); hence, this setenv is too
> late now. Mozilla software is also affected by this, see:
>
> https://bugzilla.gnome.org/show_bug.cgi?id=687763
> https://bugzilla.mozilla.org/show_bug.cgi?id=833117
>
> and many others. Firefox et al already use launcher scripts, so
> adding one more line won't be a big deal for them.
>
> >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.)
>
> Given that the only programs which seem to be *practically* affected
> by this is our Emacs, and Firefox/Thunderbird/etc. (which we don't
> have yet), and using G_SLICE=always-malloc apparently affects
> performance, I don't think that would be an appropriate solution.
>
> For now, I think you'll have to add a wrapper script.
Can anybody of you explain to me what the actual underlying problem is?
I mean, why this error message:
***MEMORY-ERROR***: [3044]: GSlice: failed to allocate 504 bytes
(alignment: 512): Function not implemented
What function is not implemented? Is that something we can fix,
perhaps in the Cygwin DLL?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-13 18:26 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
2013-08-13 18:09 ` Yaakov (Cygwin/X)
2013-08-13 18:26 ` Corinna Vinschen [this message]
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=20130813182653.GA4315@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).