unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs trunk crash
Date: Sat, 21 Mar 2015 10:14:55 +0200	[thread overview]
Message-ID: <834mpevkao.fsf@gnu.org> (raw)
In-Reply-To: <loom.20150321T002116-221@post.gmane.org>

> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Fri, 20 Mar 2015 23:21:41 +0000 (UTC)
> 
> Just got a crash with emacs/trunk/w64. The emacs used to debug this has been 
> compiled unoptimized.
> I wanted to let the mailing list know in case there is something to fix here.
> The backtrace is:
> 
> (gdb) where
> #0  0x000000040024ba41 in substitute_object_recurse (object=107071061, 
> placeholder=8607363, subtree=3)
>     at ../../emacs/src/lread.c:3306
> #1  0x000000040024b9ae in substitute_object_recurse (object=107071061, 
> placeholder=8607363,
>     subtree=107071061) at ../../emacs/src/lread.c:3299
> #2  0x000000040024b777 in substitute_object_in_subtree (object=107071061, 
> placeholder=8607363)
>     at ../../emacs/src/lread.c:3234
> #3  0x000000040024a58e in read1 (readcharfun=197175989, pch=0x8358bc, 
> first_in_list=false)
>     at ../../emacs/src/lread.c:2847

A fuller backtrace, including "xbacktrace" for the Lisp part, might
show some useful information.

Also, can you show the Lisp object being read here?

> This is the consequence of an unattented shutdown of my machine with a long 
> emacs session running. I'm not sure I'll be able to reproduce it at all. But for 
> the time being, I'm unable to restart my session. Emacs is crashing while 
> restoring one of the files of my session.

What kind of file is the file that causes the crash?  is it a Lisp
file?



  reply	other threads:[~2015-03-21  8:14 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 [this message]
2015-03-22 19:59   ` Fabrice Popineau
2015-03-22 20:13     ` Eli Zaretskii
2015-03-22 20:22     ` Eli Zaretskii
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=834mpevkao.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).