I did that when it first happened. A couple of events got thru to drracket but no stack trace.
On Feb 8, 2011, at 3:01 PM, Robby Findler wrote: > If you start drracket from the shell (I think you tend to do that?) > try hitting control-c there to see if you get a stack trace from the > break exception. > > Robby > > On Tue, Feb 8, 2011 at 1:39 PM, Matthias Felleisen <matth...@ccs.neu.edu> > wrote: >> >> I don't know how to replicate this of course, but as of today, it has become >> unresponsive to actions three times already. One of them could have been a >> release candidate but I was unable to even see the version info. >> _________________________________________________ >> For list-related administrative tasks: >> http://lists.racket-lang.org/listinfo/dev >> _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
