all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: How to debug function that uses macros
Date: Sun, 26 Feb 2017 23:36:00 -0500	[thread overview]
Message-ID: <jwv37f08d9y.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 20170226102029.34afee15@gauss

> How do I debug, using edebug, a function that uses macros?
> I want to step through the macro expansion.

Depends where the expanded code comes from.

If it comes from the macro call itself, then you'll want to add a debug
declaration to the macro, to explain which parts of the macro's
arguments are expressions.  Something like

    (defmacro foo (bar baz)
      (declare (debug (symbolp form)))
      ...)

If the expanded code you want to step through comes from the macro
itself, then you can try to use edebug-` instead of the normal `, such
as:

    (defmacro foo (bar baz)
      (declare (debug (symbolp form)))
      (edebug-\` (let ((,bar (something))) ,baz)))

> The obvious way to do this is to first create the fully 
> expanded function, then use edebug on that.  Maybe there
> is a better way, but that should work.  But how do I 
> create the fully expanded function?   Neither macroexpand
> nor macroexpand-all do anything useful here that I can tell.
> For example
>
>   (macroexpand-all '(my-function))
>
> just displays (my-function).  

Only if `my-function` is a function, in which case indeed there's
nothing to expand.


        Stefan




  reply	other threads:[~2017-02-27  4:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-26 18:20 How to debug function that uses macros Joe Riel
2017-02-27  4:36 ` Stefan Monnier [this message]
2017-03-01  6:53   ` Joe Riel
2017-03-01 13:52     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwv37f08d9y.fsf-monnier+gmane.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.