<!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"> Matthew, this afterthought of yours has been a big win for us. Since we started running our system with JIT disabled, we've consistently gotten very helpful trace info without needing Errortrace. Thanks again. (Not that I discourage anyone from using the JIT. Our system does some unusual things that I imagine might contribute to the poor error traces when combined with JIT. I will look into this in our system when time permits.) Neil Matthew Flatt wrote at 08/01/2008 11:20 AM: <blockquote cite="mid:20080801152020.C2FEE6500B7@mail-svr1.cs.utah.edu" type="cite"> <pre wrap="">At Fri, 01 Aug 2008 10:17:02 -0400, Neil Van Dyke wrote: </pre> <blockquote type="cite"> <pre wrap="">In the interim, is there anything I can do to improve the backtraces when debugging </pre> </blockquote> <pre wrap=""> One more thought: it sometimes helps to disable the JIT. The JIT and the bytecode interpreter compute stack traces in different ways, and they usually produce slightly different results. 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>