From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Ken Brown <kbrown@cornell.edu>
Cc: "9273@debbugs.gnu.org" <9273@debbugs.gnu.org>
Subject: bug#9273: 23.3; malloc initialization should (sometimes) happen at runtime
Date: Sat, 13 Aug 2011 11:07:48 -0400 [thread overview]
Message-ID: <jwvei0p4aft.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <4E468FE5.100@cornell.edu> (Ken Brown's message of "Sat, 13 Aug 2011 10:53:25 -0400")
>>> _heapinfo is indeed consistent with the current heap. But the pointer
>>> that was passed to realloc points into the old heap. So applying BLOCK
>>> to that pointer yields an absurd result. I can easily catch such cases
>>> by testing for ptr< _heapbase, as in my patch to _free_internal_nolock,
>>> but I have to figure out the best way to handle them once I've caught
>>> them.
>> malloc a buffer, then copy the contents of the old one to the new
>> one. You will have to know the size of the old block, which means you
>> will have to access the old copy of _heapinfo.
> Thanks! That's much easier than what I was trying to do.
Wouldn't it be easier to try and convince malloc to keep using the old
_heapinfo?
Stefan
next prev parent reply other threads:[~2011-08-13 15:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 20:09 bug#9273: 23.3; malloc initialization should (sometimes) happen at runtime Ken Brown
2011-08-10 0:24 ` Richard Stallman
2011-08-10 15:56 ` Eli Zaretskii
2011-08-10 17:52 ` Ken Brown
2011-08-10 18:10 ` Eli Zaretskii
2011-08-10 18:49 ` Ken Brown
2011-08-11 21:45 ` Ken Brown
2011-08-12 6:54 ` Eli Zaretskii
2011-08-12 10:10 ` Ken Brown
2011-08-12 11:33 ` Eli Zaretskii
2011-08-12 12:18 ` Ken Brown
2011-08-12 20:24 ` Ken Brown
2011-08-13 8:05 ` Eli Zaretskii
2011-08-13 13:48 ` Ken Brown
2011-08-13 14:41 ` Eli Zaretskii
2011-08-13 14:53 ` Ken Brown
2011-08-13 15:07 ` Stefan Monnier [this message]
2011-08-13 15:33 ` Ken Brown
2011-08-13 19:19 ` Stefan Monnier
2011-08-14 3:13 ` Ken Brown
2011-08-16 13:30 ` Ken Brown
2011-08-12 23:51 ` grischka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvei0p4aft.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=9273@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).