From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 18313@debbugs.gnu.org
Subject: bug#18313: 24.4.50; emacs_backtrace.txt
Date: Sat, 30 Apr 2016 15:28:04 +0200 [thread overview]
Message-ID: <87mvobrztn.fsf@gnus.org> (raw)
In-Reply-To: <83bn9di2sk.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Dec 2015 18:37:47 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: Drew Adams <drew.adams@oracle.com>, 18313@debbugs.gnu.org
>> Date: Sat, 26 Dec 2015 17:04:01 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > The assertion violation is here:
>> >
>> > #ifdef GLYPH_DEBUG
>> > /* Check that reference counts are indeed correct. */
>> > eassert (dpyinfo->reference_count == dpyinfo_refcount); <<<<<<<<
>> > eassert ((dpyinfo->terminal->image_cache == NULL
>> > && image_cache_refcount == 0)
>> > || (dpyinfo->terminal->image_cache != NULL
>> > && dpyinfo->terminal->image_cache->refcount == image_cache_refcount));
>> > #endif
>> >
>> > I guess that condition is wrong when frames are created in recursive
>> > edit.
>>
>> Should this be followed up?
>
> If this still happens, I need a recipe for debugging it.
No such recipe was given, so I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2016-04-30 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 16:20 bug#18313: 24.4.50; emacs_backtrace.txt Drew Adams
2014-08-22 13:50 ` Eli Zaretskii
2015-12-26 16:04 ` Lars Ingebrigtsen
2015-12-26 16:37 ` Eli Zaretskii
2016-04-30 13:28 ` Lars Ingebrigtsen [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=87mvobrztn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=18313@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.