From: Helmut Eller <eller.helmut@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: GSoC project - Improving ELisp Traceback and Debugging Information
Date: Fri, 05 Jun 2020 09:00:50 +0200 [thread overview]
Message-ID: <m2a71iov31.fsf@gmail.com> (raw)
In-Reply-To: 87eeqv6d30.fsf@gmail.com
On Wed, Jun 03 2020, Zach Shaftel wrote:
> Hello all,
>
> This summer I will be working on improving ELisp traceback information
> for Google Summer of Code.
Sounds very useful.
> So far I've modified the byte-code interpreter to simply store the
> offset of each funcall in the backtrace specbinding frame, and
> modified backtrace.el so the sequence of offsets is printed alongside
> each respective call in the backtrace. It's available on the
> feature/soc-bytecode-in-traceback-specbinding branch on
> Savannah.
I don't see this branch on Savannah; there's a
feature/soc-bytecode-in-traceback from 2020-04-27, but apparently
doesn't contain all this. Anyway, just wanted to say, that it would
nice if bytecode to bytecode calls would not leave the exec_byte_code
function. Those calls should push the necessary frames and continue the
interpreter loop. That way the bytecoe PC doesn't need to be saved
redundantly on the C stack and the specbinding stack.
> I've been looking at the scratch/accurate-warning-pos branch as well
> as prior discussions and am still evaluating different approaches to
> solving the task. It might be necessary to modify the way code is
> represented during compilation, be it simply with the annotated
> symbols as in that branch or with another more generalized form of
> object representation.
Instead of annotating symbols I would annotate cons cells. The reader
could keep a hash table on the side an record the source position of
cons cells.
Helmut
next prev parent reply other threads:[~2020-06-05 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 21:42 GSoC project - Improving ELisp Traceback and Debugging Information Zach Shaftel
2020-06-05 7:00 ` Helmut Eller [this message]
2020-06-06 18:20 ` Zach Shaftel
2020-06-06 19:56 ` Helmut Eller
2020-06-06 23:18 ` Zach Shaftel
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=m2a71iov31.fsf@gmail.com \
--to=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
/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).