all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: peterhull90@gmail.com, 18222@debbugs.gnu.org
Subject: bug#18222: 24.3.92; fork handlers in gmalloc.c can lead to deadlock
Date: Mon, 25 Aug 2014 05:39:58 +0300	[thread overview]
Message-ID: <83sikll2bl.fsf@gnu.org> (raw)
In-Reply-To: <wlvbphxy9w.wl%mituharu@math.s.chiba-u.ac.jp>

> Date: Mon, 25 Aug 2014 08:28:59 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: Peter Hull <peterhull90@gmail.com>, 18222@debbugs.gnu.org
> 
> I think it's worth trying also on other platforms that use gmalloc.

The problem is how to write the DUMPED and ALLOCATED_BEFORE_DUMPING
macros.  For Cygwin, they use some intimate knowledge about Cygwin
runtime internals; the question is, do other platforms have similar
facilities and features.

There's also the MinGW way of getting rid of gmalloc, but it needs a
different feature: the ability to specify a user-defined sbrk
function (which MS-Windows supports).





  reply	other threads:[~2014-08-25  2:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08 13:09 bug#18222: 24.3.92; fork handlers in gmalloc.c can lead to deadlock Ken Brown
2014-08-09  7:44 ` YAMAMOTO Mitsuharu
2014-08-09 19:24   ` Ken Brown
2014-08-11  2:16     ` Ken Brown
2014-08-11 14:44       ` Stefan Monnier
2014-08-11 15:29         ` Ken Brown
2014-08-23 16:00           ` Ken Brown
2014-08-24 23:28             ` YAMAMOTO Mitsuharu
2014-08-25  2:39               ` Eli Zaretskii [this message]
2014-08-25  4:15                 ` YAMAMOTO Mitsuharu
2014-08-25 12:17                 ` Ken Brown
2014-08-25 14:51                   ` Eli Zaretskii
2014-08-25 16:22                     ` Ken Brown
2014-08-28 14:51                       ` Ken Brown
2014-08-28 19:34                         ` Glenn Morris
2014-08-28 19:40                           ` Ken Brown

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=83sikll2bl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=18222@debbugs.gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    --cc=peterhull90@gmail.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.