From: Chang Xiaoduan <drcxd@sina.com>
To: Andrea Corallo <acorallo@gnu.org>
Cc: 67900@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#67900: 30.0.50; Emacs Crahes When Executing Command `consult-buffer'
Date: Mon, 08 Jan 2024 19:40:36 +0800 [thread overview]
Message-ID: <m3jzoknjd7.fsf@sina.com> (raw)
In-Reply-To: <yp1mstgw1sr.fsf@fencepost.gnu.org> (Andrea Corallo's message of "Mon, 08 Jan 2024 05:35:16 -0500")
Hello Andrea,
Andrea Corallo <acorallo@gnu.org> writes:
> You mean with the whole compilation unit is compiled at speed 2?
No, all the `defun', `cl-defun', and `defmacro' are declared with
`(speed 1)`.
> Mmmh not sure I understand, if you macro expanded all the instances of
> this macro how can the macro matter given it's never called?
I am very curious about this point as well. At first, I expand the macro
without the declare form in the function definition in the macro
definition. Then I add the declare form to the functions generated by
the macro expansion. To my surprise, the crash still occurs.
In another test, I add the declare form to the function definition in
the macro definition, and expanded the macros. The crash can not be
reproduced. I remove all the declare form in the generated functions,
and the crash still can not be reproduced.
Thus I come to the conclusion that the declare form in the function
definition in the macro definition is what triggers the crash.
I do not know Emacs lisp much so I convinced myself that maybe macros in
Emacs lisp is different from macros in C++ and even if there is no
instance of using the macro it still get compiled in the native
compilation. Thus, I just reported what I have observed to you.
>
> I think we have to really understand what's happening here and if what
> you've observed is reproducible cause it does not make much sense to me
> ATM.
>
> Thanks for your investigation
>
> Andrea
I guess you do not use Windows? Maybe I can setup a Windows VM so that I
can sent the VM to you and you can see the crash by yourselves. I also
wonder is there any way that we can check the C source code generated
from the Emacs lisp code before it is sent to the C compiler?
Thank you
next prev parent reply other threads:[~2024-01-08 11:40 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
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 [this message]
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=m3jzoknjd7.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).