From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: 66743@debbugs.gnu.org
Subject: bug#66743: 30.0.50; Crash when dumping reftex
Date: Wed, 25 Oct 2023 15:46:50 +0300 [thread overview]
Message-ID: <83a5s6kgxx.fsf@gnu.org> (raw)
In-Reply-To: <875y2v592c.fsf@localhost> (message from Ihor Radchenko on Wed, 25 Oct 2023 09:46:03 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Wed, 25 Oct 2023 09:46:03 +0000
>
> Steps to reproduce:
>
> emacs -Q --batch -l dump.el
>
> with dump.el
>
> (dolist (feature
> '(reftex))
> (require feature))
> (dump-emacs-portable "/tmp/emacs-dumped.dmp")
>
> backtrace:
> [...]
> Program received signal SIGABRT, Aborted.
> 0x00007ffff58d3eac in ?? () from /lib64/libc.so.6
> (gdb) bt full
> #0 0x00007ffff58d3eac in () at /lib64/libc.so.6
> #1 0x00007ffff58855c2 in raise () at /lib64/libc.so.6
> #2 0x000055555578b242 in terminate_due_to_signal (sig=6, backtrace_limit=40) at emacs.c:484
> #3 0x00005555557cadde in emacs_abort () at sysdep.c:2391
> #4 0x00005555558563f7 in dump_buffer (ctx=0x7fffffffbeb0, in_buffer=0x7ffff1e62708) at pdumper.c:2866
The code which aborts:
if (!itree_empty_p (buffer->overlays))
/* We haven't implemented the code to dump overlays. */ <<<<<<<<<<
emacs_abort ();
Any questions?
next prev parent reply other threads:[~2023-10-25 12:46 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 9:46 bug#66743: 30.0.50; Crash when dumping reftex Ihor Radchenko
2023-10-25 12:46 ` Eli Zaretskii [this message]
2023-10-25 12:58 ` Ihor Radchenko
2023-10-25 14:44 ` Stefan Kangas
2023-10-26 9:31 ` Ihor Radchenko
2023-10-26 10:01 ` Gerd Möllmann
2023-10-26 11:55 ` Ihor Radchenko
2023-10-26 12:08 ` Eli Zaretskii
2023-10-26 12:14 ` Ihor Radchenko
2023-10-26 13:04 ` Eli Zaretskii
2023-10-26 13:13 ` Ihor Radchenko
2023-10-26 13:18 ` Eli Zaretskii
2023-10-26 13:27 ` Ihor Radchenko
2023-10-26 13:28 ` Eli Zaretskii
2023-10-26 13:48 ` Ihor Radchenko
2023-10-26 15:49 ` Eli Zaretskii
2023-10-27 9:08 ` Ihor Radchenko
2023-10-27 10:38 ` Eli Zaretskii
2023-10-27 10:55 ` Ihor Radchenko
2023-10-27 11:01 ` Eli Zaretskii
2023-10-27 11:09 ` Ihor Radchenko
2023-10-27 12:36 ` Eli Zaretskii
2023-10-27 12:45 ` Ihor Radchenko
2023-10-27 12:53 ` Eli Zaretskii
2023-10-25 16:15 ` Gerd Möllmann
2023-10-25 16:21 ` Eli Zaretskii
2023-10-25 16:37 ` Gerd Möllmann
2023-10-26 7:03 ` Gerd Möllmann
2023-10-26 7:35 ` Eli Zaretskii
2023-10-26 8:04 ` Gerd Möllmann
2023-10-26 9:38 ` Ihor Radchenko
2023-10-26 9:44 ` 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=83a5s6kgxx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66743@debbugs.gnu.org \
--cc=yantar92@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).