From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: mattiase@acm.org, 61896@debbugs.gnu.org
Subject: bug#61896: 30.0.50; Emacs crashes because of an invalid free
Date: Thu, 02 Mar 2023 11:41:05 +0200 [thread overview]
Message-ID: <83mt4vebin.fsf@gnu.org> (raw)
In-Reply-To: <875ybjcz4t.fsf@posteo.net> (message from Philip Kaludercic on Thu, 02 Mar 2023 08:53:54 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: Mattias Engdegård <mattiase@acm.org>,
> 61896@debbugs.gnu.org
> Date: Thu, 02 Mar 2023 08:53:54 +0000
>
> >From what I recall, the address being freed was on the stack. How does
> the byte-code interpreter behave when the input is broken? Is there
> some way of validating if the byte-code is "coherent"? If I manually
> modify the byte code and replace random bytes, is the interpreter
> written to expect this kind of issue?
Sorry, I don't understand the questions. Maybe Mattias will.
My interpretation of this problem is that some corruption happened to
the specpdl stuff, which causes SAFE_FREE decide that some data should
be 'free'd when it was actually allocated off the stack. The question
is how could that happen.
next prev parent reply other threads:[~2023-03-02 9:41 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 [this message]
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
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=83mt4vebin.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61896@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=philipk@posteo.net \
/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).