unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ergus <spacibba@aol.com>
Cc: 37836@debbugs.gnu.org
Subject: bug#37836: 27.0.50; Snake exit not save produces segfault
Date: Mon, 21 Oct 2019 09:07:57 +0300	[thread overview]
Message-ID: <83imoi4on6.fsf@gnu.org> (raw)
In-Reply-To: <20191020195448.uyqeqnawomabzyny@Ergus> (bug-gnu-emacs@gnu.org)

> Date: Sun, 20 Oct 2019 21:54:48 +0200
> From: Ergus via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> I was playing snake and when the game ended it asked to create a
> directory. I replied no and a segfault was produced and closed emacs.
> 
> The bt in the core file was this:

Can you show the output of xbacktrace?

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.





  reply	other threads:[~2019-10-21  6:07 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 [this message]
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
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

  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=83imoi4on6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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 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).