From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 19554@debbugs.gnu.org
Subject: bug#19554: 25.0.50; void-function xref-marker-stack-empty-p and subsequent abort
Date: Sat, 10 Jan 2015 14:33:17 +0100 [thread overview]
Message-ID: <54B12A1D.3060103@gmx.at> (raw)
In-Reply-To: <8361ce7rtu.fsf@gnu.org>
> Calling the Lisp debugger in some sensitive place during creating a
> frame is known to cause this. If you can track this down and see
> why we increment the reference count of the new frame where we
> shouldn't, or declare the frame "official" too soon, perhaps this can
> be fixed. But it's a low-priority issue, because this assertion
> disappears in an optimized binary anyway.
I suppose it's the same as bug#10296 then.
> The main problem to tackle
> is why do you get a Lisp error in this scenario -- that's the real
> problem to fix.
Indeed. Another clue might be that when I try to access the menu bar
with the mouse I get
Debugger entered--Lisp error: (void-function xref-marker-stack-empty-p)
(xref-marker-stack-empty-p)
(not (xref-marker-stack-empty-p))
martin
next prev parent reply other threads:[~2015-01-10 13:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 11:43 bug#19554: 25.0.50; void-function xref-marker-stack-empty-p and subsequent abort martin rudalics
2015-01-10 12:17 ` Eli Zaretskii
2015-01-10 13:33 ` martin rudalics [this message]
2015-01-12 8:01 ` martin rudalics
2015-01-12 16:12 ` Eli Zaretskii
2015-01-12 16:35 ` martin rudalics
2015-01-12 16:48 ` Dmitry Gutov
2015-01-12 17:06 ` martin rudalics
2015-01-12 17:21 ` Eli Zaretskii
2015-01-12 17:31 ` martin rudalics
2015-01-12 18:14 ` Glenn Morris
2015-01-13 3:06 ` Dmitry Gutov
2015-01-13 15:21 ` Stefan Monnier
2015-01-13 21:21 ` Glenn Morris
2015-01-14 17:59 ` Stefan Monnier
2015-01-13 3:00 ` Dmitry Gutov
2015-01-12 17:34 ` martin rudalics
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=54B12A1D.3060103@gmx.at \
--to=rudalics@gmx.at \
--cc=19554@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.