all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Rah Guzar <rahguzar@zohomail.eu>
Cc: 61896-done@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>
Subject: bug#61896: 30.0.50; Emacs crashes because of an invalid free
Date: Tue, 5 Sep 2023 17:02:36 -0700	[thread overview]
Message-ID: <CADwFkm=t4hiGEttmvazJmoJ5GuvOV13-0ScAKt0BBz0SoLdeBg@mail.gmail.com> (raw)
In-Reply-To: <87356hvelk.fsf@zohomail.eu> (Rah Guzar's message of "Mon, 06 Mar 2023 20:52:50 +0100")

Rah Guzar <rahguzar@zohomail.eu> writes:

> Hi!
>   I tried again today and I can no longer reproduce the bug with the bytecode
>   in the site-lisp directory. The byte code hasn't been updated but my emacs
>   was updated yesterday. I have also tried building emacs-29 from source and
>   that also works fine. So it seems like the problem has been fixed.

Thanks, I'm therefore closing this bug report.





      reply	other threads:[~2023-09-06  0:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 20:25 bug#61896: 30.0.50; Emacs crashes because of an invalid free Philip Kaludercic
2023-03-02  6:15 ` Eli Zaretskii
2023-03-02  8:53   ` Philip Kaludercic
2023-03-02  9:41     ` Eli Zaretskii
2023-03-02 12:20     ` Mattias Engdegård
2023-03-02 15:21       ` Mattias Engdegård
2023-03-02 17:41         ` Philip Kaludercic
2023-03-02 10:30 ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-02 10:58   ` Philip Kaludercic
2023-03-03 10:51     ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-03 18:00       ` Philip Kaludercic
2023-03-06 19:52         ` Rah Guzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-06  0:02           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkm=t4hiGEttmvazJmoJ5GuvOV13-0ScAKt0BBz0SoLdeBg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=61896-done@debbugs.gnu.org \
    --cc=philipk@posteo.net \
    --cc=rahguzar@zohomail.eu \
    /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.