I’m working on a project where having errortrace would be nice, but it’s
a little too big to want to run without compiling anything at all. From
the errortrace documentation, it seemed like `raco setup --mode
errortrace` was just what I wanted, so I gave it a shot with a simple
program. Here are the steps I took:
$ cd /tmp/test-pkg
$ cat main.rkt
#lang racket/base
(define (foo) (values (bar)))
(define (bar) (values (baz)))
(define (baz) (values (qux)))
(define (qux) (error 'qux "kaboom!"))
(foo)
$ raco pkg install --no-setup
Linking current directory as a package
$ racket -l errortrace -l test-pkg
qux: kaboom!
errortrace...:
/tmp/test-pkg/main.rkt:5:14: (error (quote qux) "kaboom!")
/tmp/test-pkg/main.rkt:4:14: (values (qux))
/tmp/test-pkg/main.rkt:3:14: (values (baz))
/tmp/test-pkg/main.rkt:2:14: (values (bar))
$ raco setup --mode errortrace --pkgs test-pkg
<lots of raco setup output...>
$ racket -l errortrace -l test-pkg
qux: kaboom!
errortrace...:
As you can see, when running main.rkt before compiling, I got a lot of
nice errortrace output, but after running `raco setup`, I didn’t get a
stack trace, even though I used `--mode errortrace`.
Did I do something wrong? If not, is this a bug or a missing feature? If
either of the latter, is it an issue with Racket or with errortrace?
--
You received this message because you are subscribed to the Google Groups
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
