From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 16691@debbugs.gnu.org, lekktu@gmail.com
Subject: bug#16691: 24.3.50; emacs_backtrace.txt
Date: Sun, 09 Feb 2014 12:04:16 +0100 [thread overview]
Message-ID: <52F760B0.6050003@gmx.at> (raw)
In-Reply-To: <83zjm1uz1g.fsf@gnu.org>
>>> Since this started happening only lately, Martin, could you please see
>>> if some of your changes could possibly disrupt the glyph row's hash
>>> values?
>> If you told me how I could have done that, maybe. I don't have the
>> slightest idea.
>
> I don't know if you did that. I just took a look at the latest
> changes preceding the first revno where Drew reported this.
My last change before that was to process frame alpha earlier from
revision 116242. While being a very dubious change, I can't imagine how
it could affect hash values.
> As to how this could happen: did any of your changes affect the 'used'
> field of the glyph_row structure, under any circumstances?
I don't understand the glyph_row structure and hopefully never ever have
touched it. The only possibly related change is that of re-introducing
an adjust_window_margins call in window_resize_apply in revision 116307,
but this happened clearly after Bug#16660.
martin
next prev parent reply other threads:[~2014-02-09 11:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 17:30 bug#16691: 24.3.50; emacs_backtrace.txt Drew Adams
2014-02-08 19:22 ` Juanma Barranquero
2014-02-08 19:34 ` Eli Zaretskii
2014-02-08 20:06 ` martin rudalics
2014-02-08 20:31 ` Eli Zaretskii
2014-02-08 20:40 ` Glenn Morris
2014-02-08 20:55 ` Eli Zaretskii
2014-02-08 23:25 ` Glenn Morris
2014-02-09 11:04 ` martin rudalics [this message]
2014-02-09 16:30 ` Eli Zaretskii
2014-02-09 18:58 ` martin rudalics
2014-02-09 20:20 ` Eli Zaretskii
2014-02-10 8:14 ` martin rudalics
2014-02-10 17:42 ` Eli Zaretskii
2014-02-10 18:35 ` martin rudalics
2014-02-10 18:44 ` Eli Zaretskii
2015-12-26 13:26 ` Lars Ingebrigtsen
2015-12-26 13:38 ` 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=52F760B0.6050003@gmx.at \
--to=rudalics@gmx.at \
--cc=16691@debbugs.gnu.org \
--cc=eliz@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).