From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jca@wxcvbn.org, Kenichi Handa <handa@m17n.org>,
12242@debbugs.gnu.org, Chong Yidong <cyd@gnu.org>
Subject: bug#12242: Emacs 24.2 RC1 build fails on OpenBSD
Date: Thu, 23 Aug 2012 08:12:37 +0900 [thread overview]
Message-ID: <wlvcga4j2y.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <83y5l6amor.fsf@gnu.org>
>>>>> On Wed, 22 Aug 2012 19:58:12 +0300, Eli Zaretskii <eliz@gnu.org> said:
>>> 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.
> I see your point.
Sorry, I noticed that the senario I gave above was actually bogus.
Typically free will call r_alloc_sbrk(0) and check the return value
with respect to the area to be reclaimed before calling r_alloc_sbrk
with a negative argument.
Now I don't have a concrete senario to conclude that it is wrong to
change use_relocatable_buffers temporarily. I'm really sorry if my
previous posts confused you.
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2012-08-22 23:12 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
2012-08-22 16:58 ` Eli Zaretskii
2012-08-22 23:12 ` YAMAMOTO Mitsuharu [this message]
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
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=wlvcga4j2y.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=12242@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=eliz@gnu.org \
--cc=handa@m17n.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 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).