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: Mon, 07 Feb 2022 15:49:36 +0200	[thread overview]
Message-ID: <83ee4eyefj.fsf@gnu.org> (raw)
In-Reply-To: <87h79bftm7.fsf@no.workgroup> (message from Gregor Zattler on Mon, 07 Feb 2022 00:44:16 +0100)

> From: Gregor Zattler <telegraph@gmx.net>
> Cc: 53809@debbugs.gnu.org
> Date: Mon, 07 Feb 2022 00:44:16 +0100
> 
> Thread 1 "emacs-snapshot-" hit Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:408
> 408     {
> (gdb) bt full
> #0  terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:408
> #1  0x00005555557f5b38 in die (msg=0x5555559ddf05 "string_immovable_p (bytestr)", file=0x5555559ddede "bytecode.c", line=361) at alloc.c:7546
> #2  0x00005555558948b2 in exec_byte_code (bytestr=XIL(0x55555baaa9f4), vector=XIL(0x55555bad74f5), maxdepth=make_fixnum(3), args_template=0, nargs=0, args=0x0) at bytecode.c:361

In this frame #2, what is 'bytestr'?  Try this:

  (gdb) fr 2
  (gdb) p bytestr
  (gdb) xstring





  reply	other threads:[~2022-02-07 13:49 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
2022-02-06 23:44   ` Gregor Zattler
2022-02-07 13:49     ` Eli Zaretskii [this message]
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=83ee4eyefj.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).