On Sun, Jul 25, 2010 at 8:27 AM, Matthew Flatt <mfl...@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 sa...@ccs.neu.edu _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
