ok, I've been waiting for one of these squirrelly ones to come up so I can try this error trace lib out. ..
I've done something wrong here. No trace.. Line 294 is just the first line of a macro definition, so no hint as to where it is used.. .. (Haha though it is just a typo, this one is obvious..) dash el errortrace right .. racket -l errortrace §lambda1:/home/deep/liquid-parser/liquid> racket -t producer.rkt symbol->string: contract violation expected: symbol? given: "producer-type::a-simple-byte-producer" context...: /home/deep/TCA-object/liquid/object.rkt:294:4 standard-module-name-resolver §lambda1:/home/deep/liquid-parser/liquid> racket -l errortrace -t producer.rkt symbol->string: contract violation expected: symbol? given: "producer-type::a-simple-byte-producer" errortrace...: context...: /home/deep/TCA-object/liquid/object.rkt:294:4 /usr/share/racket/pkgs/errortrace-lib/errortrace/errortrace-lib.rkt:434:2: errortrace-annotate /usr/share/racket/pkgs/errortrace-lib/errortrace/errortrace-lib.rkt:482:4 standard-module-name-resolver On Sun, Nov 1, 2015 at 9:27 PM, Greg Hendershott <[email protected]> wrote: > On Fri, Oct 30, 2015 at 7:55 AM, Robby Findler > <[email protected]> wrote: > > Hi Thomas: you may wish to use errortrace to get more source locations > > for error messages. It is enabled by default in DrRacket, but you have > > to load it explicitly when you are working with the command-line > > racket. Probably racket-mode has some support for it too, but I'm not > > sure if it is turned on automatically there or not. > > In racket-mode for Emacs this is controlled by the > racket-error-context variable, which defaults to 'low. Setting it to > 'high uses errortrace. > > Also, you can have your cake and eat it, too. You can leave this set > to 'low; that's used when you C-c C-c to racket-run. But with a prefix > -- C-u C-c C-c -- it will run with errortrace. As a result, you can > use a lower level normally for speed. But if/when you get a vague > error message, you can re-run to get a better message. > > More info: > > https://github.com/greghendershott/racket-mode/blob/master/Reference.md#racket-error-context > > > Personally, I usually run with 'high / errortrace all the time. I did > however tweak the errortrace instrumentation to warn when I use `time` > or `time-apply` -- so that I don't make stupid performance claims on > the Racket mailing list. Er, I mean I added this for a friend who did > that once. :) > -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/CAGxFmCO18QmF8auP0RebT85bQdSCF9U_Co0ga4-gXpJXh-5nDQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
