unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 24640@debbugs.gnu.org
Subject: bug#24640: Crashes in 25.1
Date: Sun, 09 Oct 2016 12:57:34 +0300	[thread overview]
Message-ID: <83r37pg7zl.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdohi8TYkbDBrBWtu5pYas6aRNnH6AMnkEV1aE=62a0MPPA@mail.gmail.com> (message from Reuben Thomas on Sun, 9 Oct 2016 08:45:08 +0100)

> From: Reuben Thomas <rrt@sc3d.org>
> Date: Sun, 9 Oct 2016 08:45:08 +0100
> Cc: 24640@debbugs.gnu.org
> 
>  The only efficient way to speed up debugging (or rather to make sure
>  it succeeds at all) is for you to come up with a reproducible recipe
>  and post here all the files needed for reproducing the crashes.
> 
> ​That would seem to require me to bisect my .desktop and potentially post dozens of personal files, so doesn't
> seem feasible.​

If you just start a fresh session, save its desktop, then restart it,
while using the lazy-load feature, does it start normally?  Maybe all
that's needed is to do this, with no personal files involved.

> I thought it might be faster for you to drive a debugging session live than to engage in
> back-and-forth by email.

It would require me to explain too many things, so it won't be
efficient enough.

>  >From what I see in the backtraces, your setup fires a timer that runs
>  some complicated Lisp, and that Lisp somehow corrupts some Lisp
>  objects, which then cause crashes during GC.
> 
> ​You make it sound as though this is some arcane personal setup, when in fact I am simply using desktop.el!

So do I, but it never crashes for me.  Nor did we have such crash
reports until now.  So there's something you do that I and others
don't, although I didn't mean (and didn't say AFAIK) that it's
something arcane.

>  And the first step is
>  to stop using an optimized build, because it makes debugging much
>  harder if not impossible.
> 
> I'll see if, having rebuilt from source without optimisation, the bug still fires.​
> 
>  If you are willing to try the debugging yourself, there's some advice
>  in etc/DEBUG (search for "Debugging problems which happen in GC").
> 
> ​I'll have a look.​

Thanks.

>  Do I understand correctly that this worked for you with Emacs 24.5?
> 
> ​Yes, the identical setup loads fine in 24.5. I've never seen this sort of crash before.​

Does Emacs crash when restoring a desktop file written by Emacs 24.5,
or only when it restores files written by Emacs 25?





  reply	other threads:[~2016-10-09  9:57 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-07 23:12 bug#24640: Crashes in 25.1 Reuben Thomas
2016-10-08  5:53 ` Eli Zaretskii
2016-10-08 13:28   ` Reuben Thomas
2016-10-08 13:30   ` Reuben Thomas
2016-10-08 14:30     ` Eli Zaretskii
2016-10-08 15:26       ` Reuben Thomas
2016-10-08 15:34         ` Eli Zaretskii
2016-10-08 22:08           ` Reuben Thomas
2016-10-09  7:05             ` Eli Zaretskii
2016-10-09  7:45               ` Reuben Thomas
2016-10-09  9:57                 ` Eli Zaretskii [this message]
2016-10-09 20:21                   ` Reuben Thomas
2016-10-10  6:15                     ` Eli Zaretskii
2016-10-10 16:12                       ` Reuben Thomas
2016-10-10 16:33                         ` Eli Zaretskii
2016-10-10 17:01                           ` Reuben Thomas
2016-10-10 17:05                             ` Eli Zaretskii
2016-10-10 17:06                               ` Reuben Thomas
     [not found]                           ` <CAOnWdoheXTvdasXN8vQFZPyayZVHD-QweqJupVrS8BQFxj2iGw@mail.gmail.com>
     [not found]                             ` <831szodsus.fsf@gnu.org>
     [not found]                               ` <CAOnWdojJHhajbRcinnubLfwWhY=snydnPM7Cws9ktX+pJe8aGA@mail.gmail.com>
     [not found]                                 ` <83zimccbzr.fsf@gnu.org>
     [not found]                                   ` <CAOnWdojzYsTR=wyrn-k2dJbStej89neskr=vwZQQWrQVCGtpkA@mail.gmail.com>
2016-10-11 11:59                                     ` Eli Zaretskii
2016-10-11 14:08                                       ` Reuben Thomas
2016-10-11 14:53                                         ` Eli Zaretskii
2016-10-11 15:19                                           ` Eli Zaretskii
2016-10-11 15:42                                             ` Reuben Thomas
2016-10-11 16:26                                               ` Eli Zaretskii
2016-10-11 15:41                                           ` Reuben Thomas
2016-10-11 16:33                                             ` Eli Zaretskii
2016-10-11 16:41                                               ` Reuben Thomas
2016-10-12 10:31                                               ` Eli Zaretskii
2016-10-12 10:57                                                 ` Reuben Thomas
2016-10-12 11:14                                                   ` Eli Zaretskii
2016-10-12 13:50                                                 ` Toby Cubitt
2016-10-12 14:44                                                   ` Eli Zaretskii
2016-10-12 16:56                                                     ` Toby Cubitt
2016-10-12 17:28                                                       ` Eli Zaretskii
2016-10-12 18:07                                                         ` Toby Cubitt
2016-10-12 19:15                                                           ` Eli Zaretskii
2016-10-12 20:45                                                             ` Reuben Thomas
2016-10-14 20:06                                                               ` Eli Zaretskii

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=83r37pg7zl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24640@debbugs.gnu.org \
    --cc=rrt@sc3d.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 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).