[plt-scheme] setup-plt --mode errortrace standard-module-name-resolver: cycle in loading

Thanks, Matthew.  That will be great once you get a chance to work on it.

In the interim, is there anything I can do to improve the backtraces 
when debugging, short of deleting all ".zo"s and running with "-l 
errortrace" (which means glacial performance, due to the way we're 
running right now)?

We have a large Web app that we are moving to PLT 4.  Sometimes the 
normal MzScheme 4 backtraces have source code location info, and 
sometimes they barely tell us more than the error message and the entry 
point to our app.

Neil

Matthew Flatt wrote at 08/01/2008 09:25 AM:
> At Fri, 01 Aug 2008 05:09:18 -0400, Neil Van Dyke wrote:
>   
>> I'm having trouble with "setup-plt --mode errortrace -l" under 4.0.2.
>>     
>
> It doesn't work, because I forgot about it for v4.0. I hope to fix it
> soon.
>
> Matthew
>
> _________________________________________________
>   For list-related administrative tasks:
>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/users/archive/attachments/20080801/eded08de/attachment.html>