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

From: Sam Tobin-Hochstadt (samth at ccs.neu.edu)
Date: Sun Jul 25 11:22:19 EDT 2010

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

Posted on the dev mailing list.