From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67141@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#67141: 30.0.50; Missing element in the backtrace
Date: Mon, 13 Nov 2023 11:27:07 -0500 [thread overview]
Message-ID: <yp1il657h5w.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83sf59u4vy.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 13 Nov 2023 16:03:45 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Sun, 12 Nov 2023 17:29:27 -0500
>> From: Stefan Monnier via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Package: Emacs
>> Version: 30.0.50
>>
>>
>> emacs -Q
>> (this is an unquoted list)
>> C-j
>>
>> Gives me:
>>
>> Debugger entered--Lisp error: (void-function this)
>> (this is an unquoted list)
>> (progn (this is an unquoted list))
>> elisp--eval-last-sexp(t)
>> eval-last-sexp(t)
>> eval-print-last-sexp(nil)
>> funcall-interactively(eval-print-last-sexp nil)
>> command-execute(eval-print-last-sexp)
>>
>> But `elisp--eval-last-sexp` doesn't directly run that `progn`.
>> Instead it calls `eval` to do so. Where did `eval` go?
>>
>> I see this both in Debian's Emacs-28,2 as well as on `master`.
>> In both cases, this is using the native compiler.
>> I have a local Emacs with various patches but without using the native
>> compiler and the problem doesn't appear there.
>> So my crystal ball pointed their pointy finger at the native code compiler.
>
> Adding Andrea.
Thanks,
mmmh, my crystal ball suggests that some (native compiled) code is
calling directly a primitive (eval) without going through funcall, as a
consequence no backtrace is recorded. AFAIR that's what happen with
byte compiled code with primitves with assigned (byte)op-code as well.
BR
Andrea
next prev parent reply other threads:[~2023-11-13 16:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 22:29 bug#67141: 30.0.50; Missing element in the backtrace Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-13 14:03 ` Eli Zaretskii
2023-11-13 16:27 ` Andrea Corallo [this message]
2023-11-16 9:35 ` Andrea Corallo
2023-11-17 19:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-17 20:48 ` Andrea Corallo
2023-11-17 21:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 8:55 ` Andrea Corallo
2023-11-20 12:12 ` Eli Zaretskii
2023-11-20 13:41 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 15:13 ` Andrea Corallo
2023-11-20 17:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 18:16 ` Andrea Corallo
2023-11-20 18:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-20 21:01 ` Mattias Engdegård
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=yp1il657h5w.fsf@fencepost.gnu.org \
--to=acorallo@gnu.org \
--cc=67141@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.