[racket-dev] Weird failure w/ DrRacket

Here's a stack trace (it was easier than I thought):

vector-ref: contract violation
  expected: vector?
  given: '#s(exn-info "unsaved editor:2:0: x: unbound identifier in
module in: x" (#(14 1))
("/home/samth/sw/plt/collects/drracket/private/expanding-place.rkt:102:7")
#f)
  argument position: 1st
  other arguments...:
   1
  context...:
   /home/samth/sw/plt/collects/drracket/private/../../racket/private/map.rkt:26:19:
loop
   /home/samth/sw/plt/collects/drracket/private/module-language.rkt:1006:6:
update-error-in-defs method in .../module-language.rkt:984:4
   /home/samth/sw/plt/collects/drracket/private/module-language.rkt:2108:2:
oc-finished
   /home/samth/sw/plt/collects/mred/private/wx/common/queue.rkt:451:6
   /home/samth/sw/plt/collects/mred/private/wx/common/queue.rkt:449:3

Sam


On Fri, May 31, 2013 at 11:09 AM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> Well, if you can make it happen or get the srcloc of the vector-ref, please
> let me know. I refactored a concurrent part of online check syntax to have a
> real struct in place of a vector and boy I sure wish I had TR!  :)
>
> Robby
>
>
> On Fri, May 31, 2013 at 9:34 AM, Sam Tobin-Hochstadt <samth at ccs.neu.edu>
> wrote:
>>
>> On Fri, May 31, 2013 at 10:28 AM, Robby Findler
>> <robby at eecs.northwestern.edu> wrote:
>> > No that's a bug I introduced I think.
>> >
>> > Do you get a stack trace?
>>
>> No, unfortunately.
>>
>> >
>> >
>> > On Friday, May 31, 2013, Sam Tobin-Hochstadt wrote:
>> >>
>> >> Recently, I've been seeing the following behavior:
>> >>
>> >> - Open DrRacket on a file
>> >> - add a syntax error
>> >> - get this internal error:
>> >>
>> >> vector-ref: contract violation
>> >>   expected: vector?
>> >>   given: '#s(exn-info "post.rkt:8:0: define: bad syntax in: (define)"
>> >> (#(177 9)) () #f)
>> >>   argument position: 1st
>> >>   other arguments...:
>> >>    1
>> >>
>> >> - the definitions window goes blank, and never comes back (for that
>> >> tab).
>> >>
>> >> Disabling online compilation seems to make the problem go away.
>> >>
>> >> I assume I've done something to break my installation, but I'm not sure
>> >> what.
>> >>
>> >> Sam
>> >> _________________________
>> >>   Racket Developers list:
>> >>   http://lists.racket-lang.org/dev
>
>