From: Helmut Eller <eller.helmut@gmail.com>
To: emacs-devel@gnu.org
Cc: Rocky Bernstein <rocky@gnu.org>
Subject: Re: (How) can I position information backtraces?
Date: Mon, 18 Sep 2017 23:53:19 +0200 [thread overview]
Message-ID: <m21sn33c8g.fsf@caladan> (raw)
In-Reply-To: CANCp2gb+MDjwk7X5XGQbPdzyLJCwA+iv5GWNsas9PjA3voDoeg@mail.gmail.com
On Mon, Sep 18 2017, Rocky Bernstein wrote:
> I've been looking at Emacs Lisp code and the C source. I don't see
> how/where execution position is stored.
I suppose you want to know how Emacs stores the source position
(filename and line number) of Lisp code and in particular how the
debugger can take you from a stack frame in the backtrace to the source
position.
Emacs doesn't store such information in a nice uniform table -- sorry to
disappoint you -- instead Emacs has a bunch of heuristics to
guess/search the source position. One heuristic goes like this: first
determine the filename by searching the name of the function in the list
`load-history' or for subrs use the file etc/DOC. The line number is
not stored anywhere and is usually determined by some regexp search in
the source file.
Those heuristics work quite well for "normal" code, but are too limited
if lambdas or complex macros are involved.
There is also no nice API for this. E.g. look at
`elisp--xref-find-definitions' for the messy code that is needed for
this kind of task.
Ideally, the compiler/intepreter would generate source maps and attach
them to functions/lambdas in some way. But it seems that the motivation
for doing that (I guess it would be quite a big project) is limited,
given that the current heuristics work good enough for the simple cases.
Actually, the current approach works suprisingly well, considering how
little information is kept around.
Helmut
prev parent reply other threads:[~2017-09-18 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 16:45 (How) can I position information backtraces? Rocky Bernstein
2017-09-18 21:53 ` Helmut Eller [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=m21sn33c8g.fsf@caladan \
--to=eller.helmut@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=rocky@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).