GNU bug report logs - #67141
30.0.50; Missing element in the backtrace

Previous Next

Full log

Message #17 received at 67141 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Andrea Corallo <acorallo <at> gnu.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 67141 <at> debbugs.gnu.org
Subject: Re: bug#67141: 30.0.50; Missing element in the backtrace
Date: Fri, 17 Nov 2023 14:01:41 -0500

>> 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.
>
> PS and indeed similarly what happen calling a primitive from other C
> code.

But C code can choose whether it calls `F<foo>` directly or goes through
`Ffuncall`, whereas for ELisp code there is no such control.
It impacts debugging and profiling, in my experience.


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.