<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=UTF-8" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> 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: <blockquote cite="mid:20080801132544.339EC6500C7@mail-svr1.cs.utah.edu" type="cite"> <pre wrap="">At Fri, 01 Aug 2008 05:09:18 -0400, Neil Van Dyke wrote: </pre> <blockquote type="cite"> <pre wrap="">I'm having trouble with "setup-plt --mode errortrace -l" under 4.0.2. </pre> </blockquote> <pre wrap=""> It doesn't work, because I forgot about it for v4.0. I hope to fix it soon. Matthew _________________________________________________ For list-related administrative tasks: <a class="moz-txt-link-freetext" href="http://list.cs.brown.edu/mailman/listinfo/plt-scheme">http://list.cs.brown.edu/mailman/listinfo/plt-scheme</a> </pre> </blockquote> </body> </html>