From: Stefan Kangas <stefan@marxist.se>
To: Ergus <spacibba@aol.com>
Cc: 37836@debbugs.gnu.org
Subject: bug#37836: 27.0.50; Snake exit not save produces segfault
Date: Mon, 20 Jan 2020 12:55:17 +0100 [thread overview]
Message-ID: <87iml6tk9m.fsf@marxist.se> (raw)
In-Reply-To: <87lfq2tkkp.fsf@marxist.se> (Stefan Kangas's message of "Mon, 20 Jan 2020 12:48:38 +0100")
Stefan Kangas <stefan@marxist.se> writes:
> Are you saying that the reason for the crash was a missing directory?
> If so, could you please explain how you have arrived at this
> conclusion?
I took another look at the back trace, and what Eli writes:
> The backtrace indicates that Emacs got a SIGSEGV inside Fvector that
> was called from some timer function, but the function itself is not
> shown, AFAICT. It probably isn't related to snake at all.
I think one way of making progress here is trying to figure out which
timer function was being run at the time. Do you have any idea what
that could have been? Do you have any timer functions of your own
running? Were you doing something else in this Emacs session which it
could have been related to?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-01-20 11:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 19:54 bug#37836: 27.0.50; Snake exit not save produces segfault Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2019-10-21 6:07 ` Eli Zaretskii
2020-01-16 14:26 ` Stefan Kangas
2020-01-20 1:05 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-20 11:48 ` Stefan Kangas
2020-01-20 11:55 ` Stefan Kangas [this message]
2020-01-20 13:41 ` Jimmy Aguilar Mena
2020-01-22 9:22 ` Stefan Kangas
2020-01-22 11:25 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-01-22 18:39 ` Stefan Kangas
2020-01-23 12:41 ` Ergus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-09-22 15:34 ` Lars Ingebrigtsen
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=87iml6tk9m.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=37836@debbugs.gnu.org \
--cc=spacibba@aol.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 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.