unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Gregor Zattler <telegraph@gmx.net>
Cc: 53809@debbugs.gnu.org
Subject: bug#53809: 29.0.50; fatal error: assertion failed: string_immovable_p (bytestr)
Date: Sun, 06 Feb 2022 09:38:51 +0200	[thread overview]
Message-ID: <83zgn4zbp0.fsf@gnu.org> (raw)
In-Reply-To: <87fsox2aje.fsf@no.workgroup> (message from Gregor Zattler on Sat, 05 Feb 2022 23:50:13 +0100)

> From: Gregor Zattler <telegraph@gmx.net>
> Date: Sat, 05 Feb 2022 23:50:13 +0100
> 
> I just did a
> 
> ~/src/emacs/src$ rm -rf * ; git checkout -f ; git pull
> 
> and did (therefore a full bootstrap) make.

Did you install Emacs after rebuilding it, or did you invoke it from
the build directory?

Also, I think your setup is incorrect:

>  --enable-locallisppath=/etc/emacs:/usr/local/share/emacs/28.0/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/28.0/site-lisp:/usr/share/emacs/site-lisp

This seems to mean you are installing Emacs 29, but telling it to use
Lisp files from Emacs 28?

> I'm sorry, I was not able to isolate a minimal configuration
> which exhibits this problem.  I did a gdb bt full and
> xbacktrace, though (see below).  This gdb output is all
> gibberish to me but at the very end there I saw
> "SPECPDL_BACKTRACE".  Therefore I experimented with a
> (setq max-specpdl-size 500000) in early-init.el, but this
> did not help.

Your GDB is mis-configured wrt how it uses Python:

> #1  0x00005555555ae6ef in die (msg=msg@entry=0x5555558b70a7 "string_immovable_p (bytestr)", file=file@entry=0x5555558b7080 "bytecode.c", line=line@entry=361) at alloc.c:7546
> #2  0x00005555555b8df0 in exec_byte_codePython Exception <class 'gdb.error'> value has been optimized out:
> Python Exception <class 'gdb.error'> value has been optimized out:
> Python Exception <class 'gdb.error'> value has been optimized out:
>  (bytestr=, vector=, maxdepth=, args_template=0, nargs=0, args=<optimized out>) at bytecode.c:361

Those Python exceptions mean that the backtrace lacks important
information, and the reason is some problem with your GDB installation
and your Python installation (perhaps GDB was built with a different
version of Python than the one actually installed?).  For this reason,
it is very hard (read: impossible) to use your backtrace for trying to
diagnose the problem.  And since the backtrace is the only data you
can present that tells us what happened, it is hard to make any
progress here.

So please fix your GDB installation and produce a valid backtrace,
then post it here.  Bonus points for rebuilding Emacs without
optimizations, which would make the backtrace more accurate and
descriptive.

Thanks.





  reply	other threads:[~2022-02-06  7:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 22:50 bug#53809: 29.0.50; fatal error: assertion failed: string_immovable_p (bytestr) Gregor Zattler
2022-02-06  7:38 ` Eli Zaretskii [this message]
2022-02-06 23:44   ` Gregor Zattler
2022-02-07 13:49     ` Eli Zaretskii
2022-02-07 14:12       ` Gregor Zattler
2022-02-07 14:30         ` Eli Zaretskii
2022-02-07 15:01           ` Mattias Engdegård
2022-02-07 15:19             ` Gregor Zattler
2022-02-07 16:48               ` Mattias Engdegård
2022-02-07 18:07                 ` Gregor Zattler
2022-02-08 20:50                   ` Mattias Engdegård
2022-02-07 18:52             ` Eli Zaretskii
2022-02-07 19:09               ` Mattias Engdegård
2022-02-07 19:45                 ` Eli Zaretskii

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=83zgn4zbp0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53809@debbugs.gnu.org \
    --cc=telegraph@gmx.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).