From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Simon Pugnet <simon@polaris64.net>
Cc: 61507@debbugs.gnu.org
Subject: bug#61507: 29.0.60; "free(): invalid pointer" on latest emacs-29 commit when loading init.el
Date: Tue, 14 Feb 2023 22:29:48 +0800 [thread overview]
Message-ID: <873578uxpf.fsf@yahoo.com> (raw)
In-Reply-To: <87cz6cwdlc.fsf@polaris64.net> (Simon Pugnet's message of "Tue, 14 Feb 2023 14:01:19 +0000")
Simon Pugnet <simon@polaris64.net> writes:
> Dear Emacs maintainers,
>
> I've just built Emacs from commit
> 4bb27a5ca93f8269d9cd4b85fd948176304236eb on the emacs-29 branch and it
> fails to launch with the following message when loading my init.el
> file: -
>
> free(): invalid pointer
> Fatal error 6: Aborted
>
> Launching with -q or -Q works fine. Checking out a previous commit
> (cc30422825a5acf460d026bfe912b327b70dedcf) and rebuilding causes
> everything to work as expected again too.
>
> I've tried `make extraclean` and then `make bootstrap` in order to
> clear out any old byte-compiled or native-compiled elisp as I read
> another message earlier saying that a recent change might have caused
> a backwards incompatible change.
>
> Output of `bt full` in GDB: -
Will you please run Emacs on top of some kind of memory error checker
and see if that shows the problem's cause?
I.E. with valgrind's memcheck:
valgrind /path/to/emacs
it should complain about a double free.
next prev parent reply other threads:[~2023-02-14 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 14:01 bug#61507: 29.0.60; "free(): invalid pointer" on latest emacs-29 commit when loading init.el Simon Pugnet
2023-02-14 14:19 ` Gregory Heytings
2023-02-14 14:35 ` Simon Pugnet
2023-02-14 14:38 ` Gregory Heytings
2023-09-06 0:04 ` Stefan Kangas
2023-02-14 14:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-14 15:04 ` Simon Pugnet
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=873578uxpf.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=61507@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=simon@polaris64.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 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.