You can probably avoid starting up DrRacket to debug by calling read-language directly yourself, eg:
(read-language (open-input-string "#lang ...")) Robby On Sat, Jun 23, 2012 at 5:59 AM, Jens Axel Søgaard <[email protected]> wrote: > Hi Robby, > > Thanks for the change. Now I have a lead. I've got an > arity problem somewhere. > > /Jens Axel > > > 2012/6/22 Robby Findler <[email protected]>: >> Okay, I've pushed a change that logs errors that read-language raises >> at the debug level. Hopefully it is helpful. >> >> Robby >> >> On Fri, Jun 22, 2012 at 9:44 AM, Jens Axel Søgaard >> <[email protected]> wrote: >>> 2012/6/22 Robby Findler <[email protected]>: >>>> Oh, duh. You're right of course. >>>> >>>> FWIW, DrRacket calls read-language on a port containing the contents >>>> of the definitions window. Probably the call you're interested in is >>>> in drracket/private/module-language-tools.rkt. If you see exceptions >>>> being swallowed there, then probably I coudl add some logging code to >>>> help others avoid these problems in the future. >>> >>> That might help. If it is a wrong-path problem, then it would >>> be useful to see the path in question. >>> >>> I am seeing some strange submodule/expansion errors, so >>> perhaps something is broken in my installation? >>> Although I downloaded the latest pre-prerelease the other day, >>> I think I'll try compiling from source (just in case). >>> >>> Thanks, >>> Jens Axel > > > > -- > -- > Jens Axel Søgaard ____________________ Racket Users list: http://lists.racket-lang.org/users
