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: Tue, 11 Oct 2016 14:59:07 +0300 [thread overview]
Message-ID: <83lgxvcd10.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdojzYsTR=wyrn-k2dJbStej89neskr=vwZQQWrQVCGtpkA@mail.gmail.com> (message from Reuben Thomas on Mon, 10 Oct 2016 22:35:55 +0100)
Thanks, I've done some initial debugging. The crash seems to be
related to the variable read_objects, defined and used by lread.c. It
is an alist of objects read with the #n=object form. One of its
members is a corrupted Lisp object, which causes the GC crash when
this object is examined.
read_objects is a global variable, so it could be that some code
invoked in the middle of reading one #n=object form clobbers it by
reading another. However, I don't immediately see such forms in the
few of your many init files I looked in. Do you have any idea where
this could come from? One place they are abundant is in *.elc files,
so maybe some recursive load together with the timer-based lazy
desktop operation does that? I don't really have a working hypothesis
for now.
I'm not an expert on X tricks -- is there any way you can trick Emacs
to start a GUI session when I invoke it via SSH? Some trick with the
value of DISPLAY in the environment, perhaps? I don't need to see
what Emacs displays, just run it live under GDB. The problem that
causes the crash happens before the code I see in the backtrace --
that code just triggers GC. So it would be beneficial to run Emacs
under GDB and try to see, for example, what code changes read_objects
and how (assuming it is not changed to a non-nil value too many
times). Can this be arranged?
Thanks.
next prev parent reply other threads:[~2016-10-11 11:59 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
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 [this message]
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=83lgxvcd10.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).