From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: 74747@debbugs.gnu.org
Cc: telegraph@gmx.net, eller.helmut@gmail.com, pipcet@protonmail.com
Subject: bug#74747: 30.0.92; scratch/igc: crashes when executing M-x list-packages
Date: Mon, 09 Dec 2024 16:37:16 +0100 [thread overview]
Message-ID: <m2v7vszx3n.fsf@gmail.com> (raw)
In-Reply-To: <87seqw7ux9.fsf@no.lan> (Gregor Zattler via's message of "Mon, 09 Dec 2024 16:11:46 +0100")
Gregor Zattler via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
> Dear Emacs-developers, Gerd,
Hi Gregor (Added Pip and Helmut in CC).
> Emacs from scratch/igc started with -Q
> crashes when I do M-X list-packages. I
> produced some gdb output, see below.
>
> I wondered, if such random bug reports
> are of interest for scratch/igc at all
> (if not, please drop this bug report,
> it's in no way crucial to me) and if it
> is appropriate to post them to the bug
> tracker. I think it would be helpful if
> README-IGC would answer this two
> questions.
>
> I'm happy to answer very specifically
> specified questions.
>
> Regards, gregor
>
>
> Starting program: /home/grfz/src/emacs-igc/src/emacs --debug-init -Q -xrm --init-directory="${USER_EMACS_DIRECTORY}" --fg-daemon="${EMACS_SERVER_NAME}"
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> [Detaching after vfork from child process 823489]
> [Detaching after vfork from child process 823490]
> [Detaching after vfork from child process 823491]
>
> Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432
> 432 {
> #0 terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at ./src/emacs.c:432
> #1 0x00005555557d7c44 in set_state (state=state@entry=IGC_STATE_DEAD) at ./src/igc.c:858
> #2 0x00005555557d7c78 in igc_assert_fail (file=file@entry=0x555555902930 "igc.c", line=line@entry=586, msg=msg@entry=0x5555559022d0 "header_type (h) == IGC_OBJ_PAD || nbytes >= sizeof (struct igc_fwd)") at ./src/igc.c:209
> #3 0x00005555557d8413 in obj_size (h=h@entry=0x555555f991a0 <main_thread>) at ./src/igc.c:586
> #4 0x00005555557d843d in igc_check_fwd (client=client@entry=0x555555f991a0 <main_thread>, is_vecto
I think the above igc_check_fwd could already be the problem in itself:
ISTR that it stopped being a reliable check at some point. Maybe the
others remember more details. And maybe we should remove it, don't know.
> In GNU Emacs 31.0.50 (build 1, x86_64-pc-linux-gnu, cairo version
> 1.16.0) of 2024-12-07 built on no
> Repository revision: 308b216444b29b2d2f111d32db6d55a5322282cd
> Repository branch: scratch/igc
> Windowing system distributor 'The X.Org Foundation', version 11.0.12101007
> System Description: Debian GNU/Linux 12 (bookworm)
>
> Configured using:
> 'configure --infodir=/usr/share/info/emacs --with-json
> --with-file-notification=yes --with-libsystemd --with-cairo
> --with-x=yes --with-x-toolkit=no --without-toolkit-scroll-bars
> --without-gsettings --enable-check-lisp-object-type
> --enable-checking=yes,glyphs,igc_check_fwd,igc_debug,
> --with-mps=debug
Could you please remove the igc_check_fwd from --enable-checking and see
if it works that way?
next prev parent reply other threads:[~2024-12-09 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 15:11 bug#74747: 30.0.92; scratch/igc: crashes when executing M-x list-packages Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 15:37 ` Gerd Möllmann [this message]
2024-12-09 16:02 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 16:15 ` Gregor Zattler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 17:38 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 17:52 ` Pip Cet via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-09 20:34 ` 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=m2v7vszx3n.fsf@gmail.com \
--to=gerd.moellmann@gmail.com \
--cc=74747@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=pipcet@protonmail.com \
--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).