From: Chang Xiaoduan <drcxd@sina.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67900@debbugs.gnu.org, acorallo@gnu.org
Subject: bug#67900: 30.0.50; Emacs Crahes When Executing Command `consult-buffer'
Date: Sat, 23 Dec 2023 10:30:14 +0800 [thread overview]
Message-ID: <m37cl5d51l.fsf@sina.com> (raw)
In-Reply-To: <83msu2fzvc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 22 Dec 2023 09:41:27 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> So please build Emacs with those 3 packages (bytecomp.el, mule.el,
> startup.el) natively-compiled with native-comp-speed = 1, then
> native-compile consult.el with native-comp-speed = 2, and see if you
> still see the crashes. If yes, then consult.el is probably the one
> that triggers the bug. If compiling those 3 other packages with
> native-comp-speed = 1 eliminates the crashes, then we need to look for
> the one of those 3 which triggers the crash, and continue narrowing
> this down from there.
I have added a file-local prop-line to each of bytecomp.el, mule.el and
startup.el, which sets the `native-comp-speed` to 1. Then I rebuilt
Emacs and test with a cosnult.el with `native-comp-speed` as 2. Is this
the correct setup to test? The result: Emacs still crashes when
executing `consult-buffer`.
Further more, I have another test with `native-comp-speed` in comp.el
set to 1. That is, the default optimizaiton level for all
native-compiled lisp code is 1. Then, I add a file-local prop-line in
consult.el and set the `native-comp-speed` to 2. The result: Emacs still
crashes when executing `consult-buffer`.
I guess this is enough to confirm that the miscompiled code is in
consult.el. What should I do next?
Thanks
next prev parent reply other threads:[~2023-12-23 2:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 7:48 bug#67900: 30.0.50; Emacs Crahes When Executing Command `consult-buffer' Chang Xiaoduan
2023-12-19 13:16 ` Eli Zaretskii
[not found] ` <m3msu5751x.fsf@sina.com>
2023-12-20 13:10 ` Eli Zaretskii
2023-12-21 3:26 ` Chang Xiaoduan
2023-12-21 8:02 ` Eli Zaretskii
2023-12-21 12:40 ` Andrea Corallo
2023-12-22 3:44 ` Chang Xiaoduan
2023-12-22 7:41 ` Eli Zaretskii
2023-12-22 9:38 ` Andrea Corallo
2023-12-23 2:30 ` Chang Xiaoduan [this message]
2023-12-23 7:35 ` Eli Zaretskii
2023-12-26 8:32 ` Andrea Corallo
2023-12-28 11:44 ` Chang Xiaoduan
2023-12-29 18:37 ` Andrea Corallo
2024-01-02 7:24 ` Chang Xiaoduan
2024-01-04 9:51 ` Andrea Corallo
2024-01-05 7:04 ` Chang Xiaoduan
2024-01-05 21:46 ` Andrea Corallo
2024-01-08 3:28 ` Chang Xiaoduan
2024-01-08 10:35 ` Andrea Corallo
2024-01-08 11:40 ` Chang Xiaoduan
2024-01-09 9:58 ` Andrea Corallo
2024-01-02 8:20 ` Chang Xiaoduan
2024-01-04 9:58 ` Andrea Corallo
2024-01-05 4:22 ` Richard Stallman
2024-01-05 7:09 ` Chang Xiaoduan
2024-01-07 4:29 ` Richard Stallman
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=m37cl5d51l.fsf@sina.com \
--to=drcxd@sina.com \
--cc=67900@debbugs.gnu.org \
--cc=acorallo@gnu.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 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).