all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 15565-done@debbugs.gnu.org
Subject: bug#15565: 24.3.50; emacs_backtrace
Date: Wed, 09 Oct 2013 17:58:43 +0300	[thread overview]
Message-ID: <83ppreqyn0.fsf@gnu.org> (raw)
In-Reply-To: <CAH8Pv0hqzEnwbAxGYcHxf-_8aV3CqMRFDgMCpn8twFmsHCTi_A@mail.gmail.com>

> Date: Tue, 8 Oct 2013 22:53:04 +0200
> From: Dani Moncayo <dmoncayo@gmail.com>
> Cc: 15565@debbugs.gnu.org
> 
> >> I've just bootstrapped the latest trunk, and it crashes very easily.
> >> For example:
> >>   emacs -Q
> >>   C-h r
> >>
> >> This is the backtrace I get:
> >
> > Doesn't happen here, sorry.
> 
> Ok, I've tried to bootstrap again the latest trunk (now at revno
> 114585), and I get the same crash with the same backtrace.

I've succeeded in reproducing this.  To get hit by the bug, you need
(a) to compile with GLYPH_DEBUG=1, and (b) use a new enough compiler
that supports a non-trivial definition of 'assume'.

The problem is that 'eassert' can no longer take expressions that have
side effects, because it evaluates them twice!

I fixed this particular assertion violation in trunk revision 114590,
but I think we had better fixed 'eassert' to not have this nasty
misfeature.

(I guess no one who works on Unix compiles with GLYPH_DEBUG=1, because
the same problem was present on X.  That's too bad, since
GLYPH_DEBUG=1 is a valuable feature for weeding out bugs sooner rather
than later.)





      reply	other threads:[~2013-10-09 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 20:04 bug#15565: 24.3.50; emacs_backtrace Dani Moncayo
2013-10-08 20:11 ` Eli Zaretskii
2013-10-08 20:53   ` Dani Moncayo
2013-10-09 14:58     ` Eli Zaretskii [this message]

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=83ppreqyn0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=15565-done@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    /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.