From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Look for strace/ltrace analog for elisp.
Date: Sun, 13 May 2012 13:51:35 +0300 [thread overview]
Message-ID: <87sjf48ibs.fsf@desktop.home.int> (raw)
In order to understand how work foreign code tracing is the best technique.
Like this do strace/ltrace.
I expect ability to call something like::
(trace BODY)
and get output like::
{ foo
*{ bar
**{ concat
**} concat: result: "XXX"
**{ +
**} +: result: 20
*} bar: result: 20
} foo: result: 20
where tracer print all called functions until BODY execution was finished.
It is convenient to have ability customise output details (like enabling or
skipping input args/return value, skipping call to some functions).
But for my purpose it is important to see names of setq, defun,
declare-function, defvar, etc... because I want to debug loading of elisp
library.
I try use edebug-trace-mode but seems this is not that I look.
--
Best regards!
next reply other threads:[~2012-05-13 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 10:51 Oleksandr Gavenko [this message]
[not found] <mailman.1062.1336906313.855.help-gnu-emacs@gnu.org>
2012-05-13 14:34 ` Look for strace/ltrace analog for elisp Stefan Monnier
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=87sjf48ibs.fsf@desktop.home.int \
--to=gavenkoa@gmail.com \
--cc=help-gnu-emacs@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.
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).