From: Stefan Kangas <stefan@marxist.se>
To: Ergus <spacibba@aol.com>
Cc: Jimmy Aguilar Mena <kratsbinovish@gmail.com>, 37836@debbugs.gnu.org
Subject: bug#37836: 27.0.50; Snake exit not save produces segfault
Date: Wed, 22 Jan 2020 19:39:19 +0100 [thread overview]
Message-ID: <871rrrjpyg.fsf@marxist.se> (raw)
In-Reply-To: <20200122112552.grjhjughbtle7bhi@Ergus> (Ergus's message of "Wed, 22 Jan 2020 12:25:52 +0100")
tags 37836 + unreproducible
thanks
Ergus <spacibba@aol.com> writes:
>>> When I said yes there was not segfault anymore.
>>
>>When you saw it, were you able to reproduce it consistently using the
>>recipe you gave above?
>>
> Yes, but I can't reproduce it now doing a checkout to c2cd27bce.
I tried that too, and I can't reproduce it either. Strange.
Do you have any idea about what could have been different with your
old build? Any changes in your environment perhaps?
I'm not really sure how to investigate this beyond that. Does anyone
else have any ideas here?
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-01-22 18:39 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
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 [this message]
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=871rrrjpyg.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=37836@debbugs.gnu.org \
--cc=kratsbinovish@gmail.com \
--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).