From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs trunk crash
Date: Sun, 22 Mar 2015 22:22:09 +0200 [thread overview]
Message-ID: <837fu8srym.fsf@gnu.org> (raw)
In-Reply-To: <loom.20150322T201832-229@post.gmane.org>
> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Sun, 22 Mar 2015 19:59:41 +0000 (UTC)
>
> There is lots of bytecode which is executed during the backtrace.
> I don't know much about exploring those frames.
Ca you reproduce the problem by first starting "emacs -Q" and then
manually invoking 'desktop-read' to restore session from the offending
file?
If the above reproduces the crash, then you can produce a more
informative Lisp-level backtrace by manually loading all the Lisp
files involved as *.el files, after "emacs -Q" and before invoking
'desktop-read'. In this case, I'd begin by loading desktop.el,
frameset.el, cl-lib.el, and undeo-tree.el.
next prev parent reply other threads:[~2015-03-22 20:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 23:21 Emacs trunk crash Fabrice Popineau
2015-03-21 8:14 ` Eli Zaretskii
2015-03-22 19:59 ` Fabrice Popineau
2015-03-22 20:13 ` Eli Zaretskii
2015-03-22 20:22 ` Eli Zaretskii [this message]
2015-03-22 20:28 ` Eli Zaretskii
2015-03-22 22:35 ` Stefan Monnier
2015-03-23 15:33 ` Eli Zaretskii
2015-03-22 22:37 ` Fabrice Popineau
2015-03-23 5:32 ` Fabrice Popineau
2015-03-23 15:34 ` Eli Zaretskii
2015-03-23 20:55 ` Fabrice Popineau
2015-03-23 21:27 ` Fabrice Popineau
2015-03-24 2:28 ` Stefan Monnier
2015-03-24 17:23 ` Eli Zaretskii
2015-03-24 21:10 ` Fabrice Popineau
2015-03-25 20:38 ` Eli Zaretskii
[not found] ` <CAFgFV9MVLXraWXyVGw5=y3QWRK_5DyGf=0G6DrMLsO6gwFHSGA@mail.gmail.com>
[not found] ` <837fu2bwd3.fsf@gnu.org>
2015-03-27 10:41 ` Fabrice Popineau
2015-03-27 13:18 ` Eli Zaretskii
2015-03-21 9:59 ` 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
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=837fu8srym.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=fabrice.popineau@gmail.com \
/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).