From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12242@debbugs.gnu.org, jca@wxcvbn.org
Subject: bug#12242: Emacs 24.2 RC1 build fails on OpenBSD
Date: Wed, 22 Aug 2012 12:13:27 +0900 [thread overview]
Message-ID: <wlmx1naaaw.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <837gsrbpe9.fsf@gnu.org>
>>>>> On Wed, 22 Aug 2012 06:02:06 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> Date: Wed, 22 Aug 2012 11:35:26 +0900 From: YAMAMOTO Mitsuharu
>> <mituharu@math.s.chiba-u.ac.jp> Cc: jca@wxcvbn.org,
>> 12242@debbugs.gnu.org
>>
>> I took a look at ralloc.c a bit, and I thought that the variable
>> `use_relocatable_buffers' is not designed to be changed temporarily
>> in the first place.
> Why not? Can you tell what led you to that conclusion?
> My reading of the code is that inhibiting relocation just means that
> ralloc.c always asks for more memory when it cannot find a large
> enough block in the existing heaps.
For example, `virtual_break_value' is not updated in that case. It
can lead to an inconsistent state as reported if r_alloc_sbrk is
called with a positive argument via malloc when
use_relocatable_buffers <= 0, and then it is called with a negative
argument via free when use_relocatable_buffers > 0.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2012-08-22 3:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-20 19:53 bug#12242: Emacs 24.2 RC1 build fails on OpenBSD Jérémie Courrèges-Anglas
2012-08-21 3:03 ` Eli Zaretskii
2012-08-21 16:49 ` Eli Zaretskii
2012-08-21 19:23 ` Jérémie Courrèges-Anglas
2012-08-22 2:35 ` YAMAMOTO Mitsuharu
2012-08-22 3:02 ` Eli Zaretskii
2012-08-22 3:13 ` YAMAMOTO Mitsuharu [this message]
2012-08-22 16:58 ` Eli Zaretskii
2012-08-22 23:12 ` YAMAMOTO Mitsuharu
2012-08-23 16:06 ` Eli Zaretskii
2012-08-23 14:24 ` Chong Yidong
2012-08-23 16:16 ` Eli Zaretskii
2012-08-24 3:25 ` Chong Yidong
2012-08-24 8:46 ` 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=wlmx1naaaw.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=12242@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jca@wxcvbn.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.