unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 12242@debbugs.gnu.org, jca@wxcvbn.org, handa@m17n.org
Subject: bug#12242: Emacs 24.2 RC1 build fails on OpenBSD
Date: Thu, 23 Aug 2012 19:16:52 +0300	[thread overview]
Message-ID: <83k3wpa8i3.fsf@gnu.org> (raw)
In-Reply-To: <87vcg93cvg.fsf@gnu.org>

> From: Chong Yidong <cyd@gnu.org>
> Cc: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>,  Stefan Monnier <monnier@iro.umontreal.ca>,  Kenichi Handa <handa@m17n.org>,  jca@wxcvbn.org,  12242@debbugs.gnu.org
> Date: Thu, 23 Aug 2012 22:24:19 +0800
> 
> Let us consider outright reversion of 108048.  What would be the effect?
> Given a choice between a bug (Bug#11519) which is also in 24.1, and
> failure-to-compile on OpenBSD as a new regression, the former is far
> preferable, unless you can point out some consequence that is more
> serious that the discussion in Bug#11519 implies.

Reverting 108048 (and 108020, see below) will cause trouble to any
system that uses ralloc.c, including (evidently) OpenBSD.  The fact
that the problem was originally found only during bootstrap on Windows
is just a coincidence.  It can strike at any time that regexp search
is used in a text that includes characters which need unification.
It's a bomb waiting to explode.  So I don't recommend that.

Of course, Emacs 24.1 was shipped with that bug, so ...

Can I have a 1-day grace to try debugging the OpenBSD crash?  Jérémie
generously gave me a login on the machine where it happened, and I'd
like a chance to try debugging it.

> Also, if we revert 108048, should we revert 108020 (which is in 24.1) as
> well?  Could you explain what problem 108020 causes which 108048 is
> supposed to fix?  Does it have symptoms?

108020 had a logic flaw in the incrementing and decrementing the flag
that inhibits relocation.  Due to that flaw, the inhibition was not
really working beyond the first time.  108048 fixed that part.  And
yes, these two revisions go together.






  reply	other threads:[~2012-08-23 16:16 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
2012-08-23 16:06               ` Eli Zaretskii
2012-08-23 14:24             ` Chong Yidong
2012-08-23 16:16               ` Eli Zaretskii [this message]
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=83k3wpa8i3.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12242@debbugs.gnu.org \
    --cc=cyd@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).