Subject: bug#64613: Signalling byte ops should show up in backtraces

From: Mattias Engdegård <[email-masked]>
Date: Fri, 14 Jul 2023 16:20:37 +0200

Many byte ops don't appear in the backtrace if they signal an error. This makes it unnecessarily difficult to find the precise location of the error.

Most operations that replace a function call, such as `cdr`, `+`, `memq` and so on, have this problem.

The tricky part is to include the function in the backtrace without slowing down normal execution.