unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 6660@debbugs.gnu.org
Subject: bug#6660: xassert failure on make custom-deps
Date: Sat, 17 Jul 2010 13:07:12 +0300	[thread overview]
Message-ID: <83zkxqe81b.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTinAq7BWTW2atSFf2IMCBOdFxaGlZ-lfDz_EVTrn@mail.gmail.com>

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sat, 17 Jul 2010 02:38:22 +0200
> Cc: 
> 
> Package: emacs
> Severity: important
> Version: 24.0.50
> 
> After
> 
>   cd lisp
>   make custom-deps
> 
> or just while bootstrapping, I get a (repeatable) xassert failure on
> dispnew.c:adjust_frame_glyphs_for_frame_redisplay.

Confirmed.  "bzr bisect" blames this commit:

  cyd@stupidchicken.com-20100710185647-l4ex7uy98klo3a57
  revno: 100769
  committer: Chong Yidong <cyd@stupidchicken.com>
  branch nick: trunk
  timestamp: Sat 2010-07-10 14:56:47 -0400
  message:
    Adapt terminal frames to latest menu-bar changes.

    * frame.c (make_frame): Initialize menu_bar_lines and
    tool_bar_lines members.
    (make_initial_frame, make_terminal_frame): Initialize
    menu_bar_lines using value of menu-bar-mode.

    * msdos.c (IT_set_frame_parameters): Don't set menu-bar-lines.

The fact that matrix_dim.height and FRAME_LINES (f) differ by one
seems to agree with the diagnosis.

Can someone see if the same happens on GNU/Linux (you will need to
compile with "-DENABLE_CHECKING -DXASSERTS=1").





  reply	other threads:[~2010-07-17 10:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17  0:38 bug#6660: xassert failure on make custom-deps Juanma Barranquero
2010-07-17 10:07 ` Eli Zaretskii [this message]
2010-07-17 13:02   ` Juanma Barranquero
2010-07-17 15:30     ` Eli Zaretskii
2010-07-17 16:29       ` Juanma Barranquero
2010-07-17 16:49         ` Eli Zaretskii
2010-07-17 13:40   ` Juanma Barranquero
2010-07-17 18:35   ` Chong Yidong

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=83zkxqe81b.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=6660@debbugs.gnu.org \
    --cc=lekktu@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 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).