GNU bug report logs - #18313
24.4.50; emacs_backtrace.txt

Previous Next

Full log

Message #16 received at 18313 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 18313 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#18313: 24.4.50; emacs_backtrace.txt
Date: Sat, 26 Dec 2015 18:37:47 +0200

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: Drew Adams <drew.adams <at> oracle.com>,  18313 <at> debbugs.gnu.org
> Date: Sat, 26 Dec 2015 17:04:01 +0100
> 
> Eli Zaretskii <eliz <at> 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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.