From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
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 13:15:21 +0900 [thread overview]
Message-ID: <wlk35xqk6e.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <83sikll2bl.fsf@gnu.org>
>>>>> On Mon, 25 Aug 2014 05:39:58 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> 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.
If the system malloc always returns a 16-byte aligned address (I'm not
sure if that is the case for *BSDs), and if we actually only need
8-byte alignment for memory allocated before dumping, then we can
determine whether the address has been allocated before dumping or not
by tweaking the address returned by malloc before dumping so it always
returns a value p such that (p & 8) == 8. Actually this is how
unexec_malloc etc. in unexmacosx.c work.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2014-08-25 4:15 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
2014-08-25 4:15 ` YAMAMOTO Mitsuharu [this message]
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=wlk35xqk6e.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=18222@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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.