From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: cschol2112@googlemail.com, 10035@debbugs.gnu.org
Subject: bug#10035: Crash in check_x_frame in w32fns.c
Date: Tue, 15 Nov 2011 20:00:11 +0200 [thread overview]
Message-ID: <838vnhe05w.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SRv8W3cMCxniK1CoBzxVZUvvg=PQF0ChdY3OkALdJBN=Q@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Tue, 15 Nov 2011 18:12:47 +0100
> Cc: Christoph Scholtes <cschol2112@googlemail.com>, 10035@debbugs.gnu.org
>
> I just had another assertion failure in row_equal_p, which seems a
> variant of the bug you fixed. In this case, "pgrowx a" and "pgrowx b"
> do not show the same content, but a->hash == b->hash.
Two different rows having the same hash is not a problem -- the hash
function isn't guaranteed to be perfect. The problem is that at least
one of the hash values does not match the contents of its glyph row.
> I was just editing elisp code, and the assertion failure happened
> during an isearch for "lets".
The offending row is `a'. Is the text it shows ("Slot is the name") a
comment, displayed in font-lock-comment-face? Can you show a
screenshot?
> #2 0x0107bb11 in row_equal_p (b=0x373e968, a=0x5d4f968,
> mouse_face_p=<optimized out>) at dispnew.c:1294
^^^^^^^^^^^^^^^
??? Does GCC now optimizes even under -O0?
next prev parent reply other threads:[~2011-11-15 18:00 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-13 15:29 bug#10035: Crash in check_x_frame in w32fns.c Christoph Scholtes
2011-11-13 17:18 ` Eli Zaretskii
2011-11-13 20:04 ` Christoph Scholtes
2011-11-13 20:21 ` Eli Zaretskii
2011-11-13 20:42 ` Juanma Barranquero
2011-11-14 3:56 ` Eli Zaretskii
2011-11-14 8:57 ` Juanma Barranquero
2011-11-14 11:23 ` Eli Zaretskii
2011-11-14 11:44 ` Juanma Barranquero
2011-11-14 13:35 ` Eli Zaretskii
2011-11-14 14:29 ` Juanma Barranquero
2011-11-14 15:46 ` Juanma Barranquero
2011-11-14 17:19 ` Eli Zaretskii
2011-11-14 17:08 ` Eli Zaretskii
2011-11-14 17:20 ` Juanma Barranquero
2011-11-14 17:32 ` Juanma Barranquero
2011-11-14 17:41 ` Juanma Barranquero
2011-11-14 19:43 ` Eli Zaretskii
2011-11-14 20:18 ` Eli Zaretskii
2011-11-14 21:07 ` Juanma Barranquero
2011-11-15 0:43 ` Christoph Scholtes
2011-11-15 3:48 ` Eli Zaretskii
2011-11-15 17:12 ` Juanma Barranquero
2011-11-15 18:00 ` Eli Zaretskii [this message]
2011-11-15 19:19 ` Juanma Barranquero
2011-11-15 20:20 ` Eli Zaretskii
2011-11-15 20:28 ` Juanma Barranquero
2011-11-16 3:45 ` Eli Zaretskii
2011-11-16 23:13 ` Juanma Barranquero
2011-11-17 3:56 ` Eli Zaretskii
2011-11-18 4:17 ` Christoph Scholtes
2011-11-18 7:08 ` Eli Zaretskii
2011-11-18 12:27 ` Eli Zaretskii
2011-11-18 13:00 ` Juanma Barranquero
2011-11-13 20:55 ` Christoph Scholtes
2011-11-14 3:55 ` 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=838vnhe05w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10035@debbugs.gnu.org \
--cc=cschol2112@googlemail.com \
--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).