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: Sat, 08 Oct 2016 18:34:22 +0300 [thread overview]
Message-ID: <83eg3qhn29.fsf@gnu.org> (raw)
In-Reply-To: <CAOnWdoiA7Hf9PePOjD3LC_2gk213fhdZZSq0Q0BdzwP8snmVmw@mail.gmail.com> (message from Reuben Thomas on Sat, 8 Oct 2016 16:26:30 +0100)
> From: Reuben Thomas <rrt@sc3d.org>
> Date: Sat, 8 Oct 2016 16:26:30 +0100
> Cc: 24640@debbugs.gnu.org
>
> Well, can you tell why it crashed this time? IOW, what was the
> immediate cause of SIGSEGV?
>
> Exactly the same as before: crashed while lazy-reloading in desktop.el. At the same point as before, as far as
> I can tell.
No, I meant the immediate cause of SIGSEGV, one frame below the one
which invokes the signal handler. There must be some bad data there,
what it is?
next prev parent reply other threads:[~2016-10-08 15:34 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83eg3qhn29.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 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.