From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Andrea Corallo <acorallo@gnu.org>, 67141@debbugs.gnu.org
Subject: bug#67141: 30.0.50; Missing element in the backtrace
Date: Mon, 20 Nov 2023 22:01:49 +0100 [thread overview]
Message-ID: <2AD1FF12-25D2-4084-9EC7-727D2CF4167F@gmail.com> (raw)
In-Reply-To: <jwv5y26mwqg.fsf@iro.umontreal.ca>
> B. ELisp primitives with their own bytecode.
Some time ago I made a feeble attempt to remedy this problem but only got as far as dealing with a few byte ops that open-coded their respective Lisp operations (car, aref, and a few more).
The straightforward solution would be to access the PC and SP from a bytecode frame when a backtrace is required but it will be a bit messy and I feared there might be performance consequences, and it's possible that the stack frame format would need changing as well. Still worth a try, though.
(Actually I'd like the option to include a byte code offset to source location map in the compiled bytecode as well. It would be the next logical step. Not sure how best to store it but a byte string is probably what I'd use, possibly loaded dynamically like doc strings.)
Not sure if the native compiler would prefer building on that kind of source location structure but why not.
prev parent reply other threads:[~2023-11-20 21:01 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
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 [this message]
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=2AD1FF12-25D2-4084-9EC7-727D2CF4167F@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=67141@debbugs.gnu.org \
--cc=acorallo@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 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).