GNU bug report logs - #14569
24.3.50; bootstrap fails on Cygwin

Previous Next

Package: emacs;

Reported by: Katsumi Yamaoka <yamaoka <at> jpl.org>

Date: Fri, 7 Jun 2013 00:17:01 UTC

Severity: important

Found in version 24.3.50

Done: Ken Brown <kbrown <at> cornell.edu>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ken Brown <kbrown <at> cornell.edu>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: "14569 <at> debbugs.gnu.org" <14569 <at> debbugs.gnu.org>, Angelo Graziosi <angelo.graziosi <at> alice.it>
Subject: bug#14569: 24.3.50; bootstrap fails on Cygwin
Date: Mon, 24 Jun 2013 11:51:54 -0400
On 6/24/2013 10:34 AM, Paul Eggert wrote:
> On 06/24/2013 04:02 AM, Ken Brown wrote:
>> Can you explain why you think there's a race condition bug in Cygwin glib?
>
> It clearly has that feel.  The problem is that if one does this:
>
>    g_source_unref (g_child_watch_source_new (getpid ());
>
> at the obvious spot in Emacs startup, just as glib is
> spinning worker threads that do stuff, Emacs goes
> kaflooey.  But if one waits until the worker threads
> have stabilized (which is what the latest patch does),
> it's OK.
>
> It could be a bug in Emacs too.  Emacs's memory allocator
> isn't thread-safe, right?  And glib uses threads.  Which
> memory allocator is the Cygwin port using, exactly?  If
> it's using Emacs's allocator (i.e., compiling gmalloc.c),
> that's a bug in Emacs.  If it's using Cygwin's, it's more
> likely a bug either in the Cygwin allocator or in glib.

The Cygwin port uses Emacs's allocator.

Ken





This bug report was last modified 12 years and 1 day ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.