unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: Hit eassert introduced in r110971
Date: Mon, 08 Apr 2013 18:02:43 +0300	[thread overview]
Message-ID: <83sj31awvg.fsf@gnu.org> (raw)
In-Reply-To: <jwvk3of2nc1.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: dmantipov@yandex.ru,  emacs-devel@gnu.org
> Date: Sat, 06 Apr 2013 20:36:35 -0400
> 
> AFAIK, if this assertion fails, it means we have a problem somewhere.
> Not necessarily in update_tool_bar, but somewhere.  OTOH it is a problem
> that will very rarely cause real trouble once you deactivate
> the assertion.  So what we need to do is to add similar assertions
> elsewhere to work our way up to the root of the problem.

OK, let's investigate this.  But I don't have access to a system that
can open a GUI and a TTY frame from the same Emacs session.  So can
someone please reproduce this assertion violation and tell:

  . which frame is the selected frame at the assertion spot?

  . which code changes the selected frame and/or the selected window
    in the course of the recipe?  (this could be done by setting
    watchpoints on selected_frame and selected_window, for example.)



  parent reply	other threads:[~2013-04-08 15:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06 16:35 Hit eassert introduced in r110971 Dmitry Antipov
2013-04-06 18:37 ` Eli Zaretskii
2013-04-06 19:16   ` Eli Zaretskii
2013-04-07  0:36     ` Stefan Monnier
2013-04-07  2:49       ` Eli Zaretskii
2013-04-07 13:50         ` Stefan Monnier
2013-04-07 15:37           ` Eli Zaretskii
2013-04-07 17:54             ` Stefan Monnier
2013-04-08 15:02       ` Eli Zaretskii [this message]
2013-04-08 17:40         ` Stefan Monnier

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=83sj31awvg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dmantipov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).