With last night's build, the error message is now:<br><br>cm: no SHA-1 for dependency: #"C:\\Documents and Settings\\williamsm\\My Documents\\Development\\madness\\madness.rkt"<br><br>I am using a development link (using PLaneT) to reference the madness (which is an acronym for Multi-Agent Dynamic Network Simulation System - MADNeSS, not a reference to my mental state) development folder. But, the files in it are actually .ss files - as are all of the files involved. So, I'm guessing that somewhere along the line the development link to (planet williams/madness/madness) didn't 'remember' it was to a .ss file instead of a .rkt file.<br> <br>Doug<br><br><div class="gmail_quote">On Sun, Jul 25, 2010 at 2:49 PM, Doug Williams <span dir="ltr"><<a href="mailto:m.douglas.williams@gmail.com" target="_blank">m.douglas.williams@gmail.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Sam appears to be corrects.<br><br>If "No Debugging or profiling" is selected, I get the backtrace. If "Debugging" is selected, I only get the error message. And, most interestingly, if "Debugging and profiling" is selected, it runs correctly.<br> <br>Also, Robby's suspicion that it would run correctly if "Populate compiled/ directories (for faster loading)" is unchecked, seems to be true. It does run when it is unchecked.<br><font color="#888888"><br> Doug</font><div><div></div><div><br><br><div class="gmail_quote"> On Sun, Jul 25, 2010 at 9:22 AM, Sam Tobin-Hochstadt <span dir="ltr"><<a href="mailto:samth@ccs.neu.edu" target="_blank">samth@ccs.neu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div>On Sun, Jul 25, 2010 at 8:27 AM, Matthew Flatt <<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>> wrote:<br> ><br> > It's worrying, though, that you're getting a DrRacket backtrace that<br> > covers "cm.rkt". Files in the main installation normally should not be<br> > instrumented for backtraces. Does your installation have any "drracket"<br> > subdirectories of any "compiled" directories?<br> <br> </div>It's easy to get such a backtrace if "Debugging" (meaning Errortrace<br> Debugging) is off. This is particularly likely to be what happened<br> here, since every backtrace frame is a function definition, which<br> rarely happens with errortrace, but always happens with the internal<br> Racket backtraces.<br> <font color="#888888">--<br> sam th<br> <a href="mailto:samth@ccs.neu.edu" target="_blank">samth@ccs.neu.edu</a><br> </font></blockquote></div><br> </div></div></blockquote></div><br>