Thanks for figuring this out!
Robby
On Sun, May 4, 2014 at 7:30 PM, Geoffrey S. Knauth wrote:
> I'm happy to say that with that particular @interaction[...] deleted, the
> rest of the build completed quickly and I now have a working DrRacket 6.0.1.6.
>
> Geoff
>
_
Rack
I'm happy to say that with that particular @interaction[...] deleted, the rest
of the build completed quickly and I now have a working DrRacket 6.0.1.6.
Geoff
_
Racket Developers list:
http://lists.racket-lang.org/dev
On May 4, 2014, at 20:14 , Robby Findler wrote:
> Oh! Well that code is clearly broken!
> I guess you have a cyclic symbolic link in your temporary directory?
> Or maybe just a ton of stuff?
> Unless you want to, I'll push a change somehow or other.
My /tmp looks like this:
/tmp:
-rw---
Oh! Well that code is clearly broken!
I guess you have a cyclic symbolic link in your temporary directory?
Or maybe just a ton of stuff?
Unless you want to, I'll push a change somehow or other.
Robby
On Sun, May 4, 2014 at 7:09 PM, Geoffrey S. Knauth wrote:
> On May 4, 2014, at 19:20 , Robby F
On May 4, 2014, at 19:20 , Robby Findler wrote:
> start throwing stuff out of it (running it at the command-line, not in
> drracket)
> until I got very small and and still had the bad behavior.
I'm already small and have bad behavior, but I get your point.
> PS: thanks for taking this on!
Tha
Okay, that's just bizarre. If this were my machine, the next step I'd
take would be to make a copy of that file and start throwing stuff out
of it (running it at the command-line, not in drracket) until I got
very small and and still had the bad behavior. Like start by throwing
away everything afte
Does this help? --Geoff
$ racket -l scribblings/guide/let.scrbl
GSK-1
GSK-2
C-c C-cuser break
context...:
/Users/gknauth/test/plt/git/plt/pkgs/sandbox-lib/racket/sandbox.rkt:883:2:
user-eval
/Users/gknauth/test/plt/git/plt/pkgs/scribble-pkgs/scribble-lib/scribble/eval.rkt:399:0:
do-p
The stack traces suggest it is in that one file. So if you open it up
and put a printf right before each example and then see when the
printfs stop, that'll probably tell us something good. You'd want to
look for each place where there is an example (compare the
documentation itself to the source)
I'm happy to insert printfs in my tree if you tell me where. --Geoff
On May 4, 2014, at 17:33 , Robby Findler wrote:
> thanks. Unfortunately I cannot reproduce this on my machine but the thing I
> would do if I could would be to start putting printfs in to try to find a
> smaller programs tha
thanks. Unfortunately I cannot reproduce this on my machine but the thing I
would do if I could would be to start putting printfs in to try to find a
smaller programs that gets stuck.
Robby
On Sunday, May 4, 2014, Geoffrey S. Knauth wrote:
> On May 4, 2014, at 16:44 , Robby Findler
> >
> wrote
On May 4, 2014, at 16:44 , Robby Findler wrote:
> That suggests to me that it is running of the of the examples in
>
> /Users/gknauth/test/plt/git/plt/pkgs/racket-pkgs/racket-doc/scribblings/guide/let.scrbl
> that's causing the problem. Does this terminate:
> $ racket -l scribblings/guide/le
That suggests to me that it is running of the of the examples in
/Users/gknauth/test/plt/git/plt/pkgs/racket-pkgs/racket-doc/scribblings/guide/let.scrbl
that's causing the problem. Does this terminate:
$ racket -l scribblings/guide/let.scrbl
Robby
On Sun, May 4, 2014 at 3:32 PM, Geoffrey S. Kn
Thanks. I'm in the middle of build attempt #3. If it gets stuck, WILCO (I
will comply). It's currently roaring along. Next winter I think I'll heat my
house with raco setup. --Geoff
On May 4, 2014, at 16:15 , Robby Findler wrote:
> I don't know what's causing that problem, but it looks to
On May 4, 2014, at 16:01 , Geoffrey S. Knauth wrote:
> I did a ^C, restarted make, it blew through all the stuff it did before, and
> now is taking a long time building the documentation again, currently again
> at 100% CPU here:
>
> raco setup: --- building documentation ---
> raco setup: 7 r
I don't know what's causing that problem, but it looks to me like we
might get some good information if you do this:
% racket -l scribblings/guide/guide.scrbl
and then let it get good and stuck and hit control-c. You should get a
stack trace and that stack trace might be illuminating...
Robby
15 matches
Mail list logo
