From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>, Rich Felker <dalias@libc.org>
Cc: emacs-devel@gnu.org
Subject: Re: Dumper issue, revisited; invalid realloc/free
Date: Wed, 04 Feb 2015 15:34:40 -0500 [thread overview]
Message-ID: <54D28260.40403@cornell.edu> (raw)
In-Reply-To: <83lhkdfpgc.fsf@gnu.org>
On 2/4/2015 2:26 PM, Eli Zaretskii wrote:
>> Date: Wed, 4 Feb 2015 14:13:05 -0500
>> From: Rich Felker <dalias@libc.org>
>> Cc: emacs-devel@gnu.org
>>
>>> Yes. Several platforms (Cygwin and MinGW on MS-Windows) already do
>>> exactly that.
>>
>> Where is the code that does this? I don't see it in alloc.c.
>
> The Cygwin code is in sheap.c, the MinGW code is in w32heap.c.
>
>> Is it only used when system_malloc=no? The case where it's really
>> needed is for system_malloc=yes...
>
> MinGW uses that with system malloc. Not sure about Cygwin.
Cygwin (in the master branch) uses gmalloc.c before dumping and the system
malloc after dumping. See the code in gmalloc.c involving HYBRID_MALLOC.
Ken
next prev parent reply other threads:[~2015-02-04 20:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 17:57 Dumper issue, revisited; invalid realloc/free Rich Felker
2015-02-04 19:08 ` Eli Zaretskii
2015-02-04 19:13 ` Rich Felker
2015-02-04 19:22 ` Eli Zaretskii
2015-02-04 19:26 ` Eli Zaretskii
2015-02-04 20:34 ` Ken Brown [this message]
2015-02-05 1:31 ` Rich Felker
2015-02-05 3:25 ` Rich Felker
2015-02-05 3:48 ` Eli Zaretskii
2015-02-05 4:33 ` Rich Felker
2015-02-05 16:14 ` Wolfgang Jenkner
2015-02-05 18:43 ` Rich Felker
2015-02-04 19:21 ` Eli Zaretskii
2015-02-04 19:37 ` Rich Felker
2015-02-04 19:44 ` Eli Zaretskii
2015-02-04 19:49 ` Rich Felker
2015-02-04 19:54 ` Eli Zaretskii
2015-02-04 20:02 ` Rich Felker
2015-02-04 20:36 ` Eli Zaretskii
2015-02-04 20:08 ` Rich Felker
2015-02-04 20:40 ` Eli Zaretskii
2015-02-04 22:17 ` Rich Felker
2015-02-05 3:42 ` Eli Zaretskii
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=54D28260.40403@cornell.edu \
--to=kbrown@cornell.edu \
--cc=dalias@libc.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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.