From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
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:17:33 +0200 [thread overview]
Message-ID: <8361ce7rtu.fsf@gnu.org> (raw)
In-Reply-To: <54B11070.6050504@gmx.at>
> Date: Sat, 10 Jan 2015 12:43:44 +0100
> From: martin rudalics <rudalics@gmx.at>
>
> With today's trunk/master and _my init files_ I currently see the
> following problem. After coming up with the initial frame and hitting
> C-x 5 2 I get
>
> Debugger entered--Lisp error: (void-function xref-marker-stack-empty-p)
> (xref-marker-stack-empty-p)
> (not (xref-marker-stack-empty-p))
> x-create-frame(((visibility) (bottom-divider-width . 6) (right-divider-width . 6) (horizontal-scroll-bars . t) (tool-bar-lines . 0)))
> x-create-frame-with-faces(((bottom-divider-width . 6) (right-divider-width . 6) (horizontal-scroll-bars . t) (cursor-color . "red3") (tool-bar-lines . 0)))
> make-frame()
> make-frame-command()
> funcall-interactively(make-frame-command)
> call-interactively(make-frame-command nil nil)
> command-execute(make-frame-command)
>
> and no frame is created. I leave the Backtrace open and do C-x 5 2.
> Now a new frame is created. If I now do C-x C-c Emacs decides to die as
> follows.
>
> Breakpoint 1, terminate_due_to_signal (sig=22, backtrace_limit=2147483647) at emacs.c:352
> 352 signal (sig, SIG_DFL);
> (gdb) bt
> #0 terminate_due_to_signal (sig=22, backtrace_limit=2147483647) at emacs.c:352
> #1 0x0118363a in die (msg=0x14c1575 "glyph_matrix_count == 0", file=0x14c10dc "dispnew.c", line=2260) at alloc.c:7138
> #2 0x0100693b in check_glyph_memory () at dispnew.c:2260
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. The main problem to tackle
is why do you get a Lisp error in this scenario -- that's the real
problem to fix.
next prev parent reply other threads:[~2015-01-10 12:17 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 [this message]
2015-01-10 13:33 ` martin rudalics
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=8361ce7rtu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=19554@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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.