From: Jacob Faibussowitsch <jacob.fai@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 62504@debbugs.gnu.org
Subject: bug#62504: 30.0.50; SEGFAULT On M-x
Date: Wed, 29 Mar 2023 08:29:06 -0400 [thread overview]
Message-ID: <B437A748-5BCE-4C1B-9593-2BDF1E792394@gmail.com> (raw)
In-Reply-To: <xjfy1ngeybz.fsf@ma.sdf.org>
Looks like I jumped the gun on blaming the segfaults on 52b67740d10df8ca539fdc2c7d50283997683141. They still happen before it. Interestingly they only appear to happen if the `(wrong-number-of-arguments #<subr signal> 2)` error has not fired.
For example, my setup lazy-loads many packages (among them yasnippet and auto-complete) on an idle timer or eagerly if I invoke/reference an auto-loaded symbol. If I wait for the idle timer to lazy load e.g. yasnippet then I get `(wrong-number-of-arguments #<subr signal> 2)`. But if I try to eagerly load yasnippet via auto-load then I get a segfault instead.
I don’t know how to reliably reproduce this unfortunately...
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Mar 29, 2023, at 04:49, Andrea Corallo <akrl@sdf.org> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Jacob Faibussowitsch <jacob.fai@gmail.com>
>>> Date: Tue, 28 Mar 2023 11:25:49 -0400
>>>
>>> This bug is twofold and appears to be related to bug#62446 and bug#61917. I produce a much smaller reproducer that generates the same kind of error as bug#61917, namely `(wrong-number-of-arguments #<subr signal> 2)`. Segfaults only occur after the following commit:
>>>
>>> commit 52b67740d10df8ca539fdc2c7d50283997683141
>>> Author: Mattias Engdegård <mattiase@acm.org>
>>> Date: Sat Mar 25 15:38:00 2023 +0100
>>>
>>> Generalise a LAP optimisation rule
>>>
>>> * lisp/emacs-lisp/byte-opt.el (byte-optimize-lapcode):
>>> Accept (stack-set 1) as equivalent to (discardN-preserve-tos 1) in a
>>> rule previously overlooked. This is usually beneficial in code size
>>> and almost always shortens dynamic paths.
>>>
>>>
>>> Common setup:
>>>
>>> 1. mkdir repro
>>> 2. Put attached init.el and main.c inside (technically, main.c need not be in repro)
>>>
>>> ———
>>>
>>> To reproduce bug#61917:
>>>
>>> 1. git checkout master
>>> 2. configure --with-native-compilation \
>>> --without-x \
>>> --without-ns \
>>> --without-compress-install \
>>> --with-native-compilation \
>>> --with-json \
>>> --with-tree-sitter
>>> 3. make bootstrap
>>> 4. emacs --init-directory ../repro
>>> 5. Check messages, and ye shall find the bug message.
>>>
>>> ———
>>>
>>> To reproduce segfault:
>>>
>>> 1. git checkout 52b67740d10df8ca539fdc2c7d50283997683141
>>> 2. Perform same configure and build commands as above.
>>> 3. emacs --init-directory ../repro ../repro/main.c (loading main.c is *required*, the segfault does not fire otherwise)
>>> 4. (In emacs) M-x
>>> 5. Fatal error 11: Segmentation fault
>>
>> Thanks.
>>
>> Andrea, maybe this will help you investigate the issue.
>
> Yep, noted thanks.
>
> Andrea
next prev parent reply other threads:[~2023-03-29 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 15:25 bug#62504: 30.0.50; SEGFAULT On M-x Jacob Faibussowitsch
2023-03-28 17:01 ` Eli Zaretskii
2023-03-29 8:49 ` Andrea Corallo
2023-03-29 12:29 ` Jacob Faibussowitsch [this message]
2023-03-29 15:27 ` Andrea Corallo
2023-03-29 15:31 ` Jacob Faibussowitsch
2023-09-11 23:56 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B437A748-5BCE-4C1B-9593-2BDF1E792394@gmail.com \
--to=jacob.fai@gmail.com \
--cc=62504@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=eliz@gnu.org \
/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.