[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#67141: 30.0.50; Missing element in the backtrace
From: |
Andrea Corallo |
Subject: |
bug#67141: 30.0.50; Missing element in the backtrace |
Date: |
Mon, 13 Nov 2023 11:27:07 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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
- bug#67141: 30.0.50; Missing element in the backtrace, Stefan Monnier, 2023/11/12
- bug#67141: 30.0.50; Missing element in the backtrace, Eli Zaretskii, 2023/11/13
- bug#67141: 30.0.50; Missing element in the backtrace,
Andrea Corallo <=
- bug#67141: 30.0.50; Missing element in the backtrace, Andrea Corallo, 2023/11/16
- bug#67141: 30.0.50; Missing element in the backtrace, Stefan Monnier, 2023/11/17
- bug#67141: 30.0.50; Missing element in the backtrace, Andrea Corallo, 2023/11/17
- bug#67141: 30.0.50; Missing element in the backtrace, Stefan Monnier, 2023/11/17
- bug#67141: 30.0.50; Missing element in the backtrace, Andrea Corallo, 2023/11/20
- bug#67141: 30.0.50; Missing element in the backtrace, Eli Zaretskii, 2023/11/20
- bug#67141: 30.0.50; Missing element in the backtrace, Stefan Monnier, 2023/11/20
- bug#67141: 30.0.50; Missing element in the backtrace, Andrea Corallo, 2023/11/20
- bug#67141: 30.0.50; Missing element in the backtrace, Stefan Monnier, 2023/11/20
- bug#67141: 30.0.50; Missing element in the backtrace, Andrea Corallo, 2023/11/20