From: Stefan Kangas <stefan@marxist.se>
To: rms@gnu.org
Cc: 50339-done@debbugs.gnu.org
Subject: bug#50339: master creashed in compact_small_strings
Date: Tue, 21 Sep 2021 00:41:37 -0700 [thread overview]
Message-ID: <CADwFkmk1nvp_Q3SdY7w9uRxD83+vCrHZXLapR=z690Bm1Q+yeg@mail.gmail.com> (raw)
In-Reply-To: <E1mST1K-0000js-QS@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> > > Alas, my machine crashed and that session was lost.
>
> > Should this bug remain open, or does that preclude us making any further
> > progress here?
>
> I can't do any further debugging on the process which crashed.
> So I can't contribute any further for the moment.
> Whether to close the ticket isup to you.
>
> > I can see that you discussed that this might have been
> > caused by a hardware issue.
>
> That was just speculation, of course. But I could not see how obeying
> the instructions in that code could have produced this result.
>
> Perhaps a bug in a signal handler could have done it.
OK, let's close it for now then, under the assumption that there is not
much we can do to make any progress here given that the session was
lost.
I suppose that our best chance to catch it, if it is indeed a bug in our
code, would be for someone to run into this crash again. For better or
for worse.
prev parent reply other threads:[~2021-09-21 7:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 16:04 bug#50339: master creashed in compact_small_strings Richard Stallman
2021-09-02 16:12 ` Eli Zaretskii
2021-09-04 17:18 ` Richard Stallman
2021-09-04 17:35 ` Eli Zaretskii
2021-09-06 3:08 ` Richard Stallman
2021-09-06 5:42 ` Eli Zaretskii
2021-09-07 3:17 ` Richard Stallman
2021-09-07 6:14 ` Eli Zaretskii
2021-09-08 3:27 ` Richard Stallman
2021-09-19 16:05 ` Stefan Kangas
2021-09-20 23:48 ` Richard Stallman
2021-09-21 7:41 ` Stefan Kangas [this message]
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='CADwFkmk1nvp_Q3SdY7w9uRxD83+vCrHZXLapR=z690Bm1Q+yeg@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=50339-done@debbugs.gnu.org \
--cc=rms@gnu.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).