From: Rah Guzar via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 61896@debbugs.gnu.org
Subject: bug#61896: 30.0.50; Emacs crashes because of an invalid free
Date: Mon, 06 Mar 2023 20:52:50 +0100 [thread overview]
Message-ID: <87356hvelk.fsf@zohomail.eu> (raw)
In-Reply-To: <87h6v1yasm.fsf@posteo.net>
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.
Philip Kaludercic <philipk@posteo.net> writes:
> Rah Guzar <rahguzar@zohomail.eu> writes:
>
>> I have never used gdb before so I will need to figure that out. I am traveling
>> today so this will not happen before Monday or Tuesday. But I will try it
>> sometime next week.
>
> It shouldn't be that difficult, I usually first reconfigure Emacs with
> debugging information:
>
> $ pwd
> /home/user/src/emacs/
> $ ./configure CFLAGS="-ggdb3"
>
> Then all you need to do is to start Emacs in the src sub-directory using
> GDB and then try to provoke the bug:
>
> $ pwd
> /home/user/src/emacs/src
> $ gdb emacs |& tee error.log
> ... # Copyright and stuff here.
> (gdb) run -Q
> ... # Emacs is running now and you can load the broken bytecode.
> # The next GDB prompt will appear when Emacs aborts.
> (gdb) xbacktrace
> ... # The Lisp backtrace should appear here.
> (gdb) quit
>
> If you do this, then the entire session log should be store in the
> "error.log" file.
next prev parent reply other threads:[~2023-03-06 19:52 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 [this message]
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=87356hvelk.fsf@zohomail.eu \
--to=bug-gnu-emacs@gnu.org \
--cc=61896@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 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).