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 "Popu
I've pushed the splice-at-file-level change so we can try it out.
There are many uses of `collection-path' that should change to
`collection-file-path'. Most would be easy to change, but as expected,
that's not always the case. For a while, I think file-level splicing
will work well only for colle
At Sun, 25 Jul 2010 11:22:19 -0400, Sam Tobin-Hochstadt wrote:
> On Sun, Jul 25, 2010 at 8:27 AM, Matthew Flatt 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 backtr
On Sun, Jul 25, 2010 at 8:27 AM, Matthew Flatt 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
The immediate bug is now fixed (to show up in a nightly build until
tomorrow).
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"
subdire
5 matches
Mail list logo
