From: Eli Zaretskii <eliz@gnu.org>
To: Dima Kogan <dima@secretsauce.net>
Cc: 21999@debbugs.gnu.org, eggert@cs.ucla.edu, deng@randomsample.de
Subject: bug#21999: 25.0.50; Binary with --enable-checking immediately aborts with '0<=size'
Date: Tue, 24 Nov 2015 18:12:59 +0200 [thread overview]
Message-ID: <83bnajz88k.fsf@gnu.org> (raw)
In-Reply-To: <87poyzzpph.fsf@secretsauce.net>
> From: Dima Kogan <dima@secretsauce.net>
> Cc: David Engster <deng@randomsample.de>, Paul Eggert <eggert@cs.ucla.edu>, 21999@debbugs.gnu.org
> Date: Tue, 24 Nov 2015 01:55:38 -0800
>
> This comes from recent changes that created gc_asize() for use in
> the GC, and changed ASIZE() to eassume() if we're not in the GC:
>
> https://github.com/emacs-mirror/emacs/commit/8afaa1321f808#diff-0e5d67da0ba3fb5c2886841cb3d0ccecR1547
>
> This is a very recent change, so we're now seeing some of the effects.
> In this particular case FONT_ENTITY_P() was called from the GC; it
> called ASIZE(), which saw a marked object so we barfed in the eassume().
> This eassume() is only fatal if --enable-checking, which is why that is
> significant.
>
> I don't know what the plan is here, so no patch is attached. Cc-ing
> Paul, since he authored the patch in question.
Right, thanks. That eassume in ASIZE made any macro that uses ASIZE
unsafe to use in the garbage collector.
I fixed this in commit d5fdffe, but I suggest that we reconsider that
eassume. After all, the size field of the pseudo-vector object is not
really a size, but a bunch of bitfields, so I'm not sure testing it in
its entirety makes sense. Paul?
David, please see that your problem is solved now.
Thanks.
next prev parent reply other threads:[~2015-11-24 16:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 19:52 bug#21999: 25.0.50; Binary with --enable-checking immediately aborts with '0<=size' David Engster
2015-11-23 20:22 ` Eli Zaretskii
2015-11-23 21:05 ` David Engster
2015-11-24 9:55 ` Dima Kogan
2015-11-24 16:12 ` Eli Zaretskii [this message]
2015-11-24 16:32 ` David Engster
2020-08-15 6:05 ` Stefan Kangas
2015-11-25 7:52 ` Paul Eggert
2015-11-25 17:34 ` 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=83bnajz88k.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21999@debbugs.gnu.org \
--cc=deng@randomsample.de \
--cc=dima@secretsauce.net \
--cc=eggert@cs.ucla.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).