[racket-dev] no backtrace for error in macro

From: Robby Findler (robby at eecs.northwestern.edu)
Date: Tue Nov 8 13:18:49 EST 2011

On Tue, Nov 8, 2011 at 12:17 PM, Jon Rafkind <rafkind at cs.utah.edu> wrote:
> I guess runtime stack traces won't help. It would be nice to see all the locations the syntax went through in its lifetime. Maybe it could be stored as a syntax property?

You mean you could, say, click on some subexpression in step N and
then go back one step and find that expression (if it still exists) in
the previous step in the stepper?


Posted on the dev mailing list.