[racket-dev] Can't Find a Workaround for Bug 11017 in DrRacket

Sam appears to be corrects.

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.

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.

Doug

On Sun, Jul 25, 2010 at 9:22 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>wrote:

> On Sun, Jul 25, 2010 at 8:27 AM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
> >
> > It's worrying, though, that you're getting a DrRacket backtrace that
> > covers "cm.rkt". Files in the main installation normally should not be
> > instrumented for backtraces. Does your installation have any "drracket"
> > subdirectories of any "compiled" directories?
>
> It's easy to get such a backtrace if "Debugging" (meaning Errortrace
> Debugging) is off.  This is particularly likely to be what happened
> here, since every backtrace frame is a function definition, which
> rarely happens with errortrace, but always happens with the internal
> Racket backtraces.
> --
> sam th
> samth at ccs.neu.edu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.racket-lang.org/dev/archive/attachments/20100725/2c3b9c2c/attachment.html>