Sam appears to be corrects.<br><br>If &quot;No Debugging or profiling&quot; is selected, I get the backtrace. If &quot;Debugging&quot; is selected, I only get the error message. And, most interestingly, if &quot;Debugging and profiling&quot; is selected, it runs correctly.<br>
<br>Also, Robby&#39;s suspicion that it would run correctly if &quot;Populate compiled/ directories (for faster loading)&quot; is unchecked, seems to be true. It does run when it is unchecked.<br><br>Doug<br><br><div class="gmail_quote">
On Sun, Jul 25, 2010 at 9:22 AM, Sam Tobin-Hochstadt <span dir="ltr">&lt;<a href="mailto:samth@ccs.neu.edu">samth@ccs.neu.edu</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Sun, Jul 25, 2010 at 8:27 AM, Matthew Flatt &lt;<a href="mailto:mflatt@cs.utah.edu">mflatt@cs.utah.edu</a>&gt; wrote:<br>
&gt;<br>
&gt; It&#39;s worrying, though, that you&#39;re getting a DrRacket backtrace that<br>
&gt; covers &quot;cm.rkt&quot;. Files in the main installation normally should not be<br>
&gt; instrumented for backtraces. Does your installation have any &quot;drracket&quot;<br>
&gt; subdirectories of any &quot;compiled&quot; directories?<br>
<br>
</div>It&#39;s easy to get such a backtrace if &quot;Debugging&quot; (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">samth@ccs.neu.edu</a><br>
</font></blockquote></div><br>