I think this is now fixed.
To catch up the list: We tracked down the problem to an incorrectly
encoded instruction. Most processors (and the gdb disassembler)
apparently don't care about the bits that were incorrect, but Deren's
does.
As you can imagine, it did not immediately occur to us to chec
Hi Matthew,
I get
Attaching to process 13920
Reading symbols from
/root/racket/racket-6.0.1/src/build/racket/racketcgc...done
.
[lots of loads omitted]
0x01b230f8 in ?? ()
(gdb) bt
#0 0x01b230f8 in ?? ()
#1 0x40826940 in ?? ()
#2 0x40826940 in ?? ()
Backtrace stopped: previous frame identical t
I don't have a great idea, but can you use gdb to attach to the
spinning "racketcgc" process (that's running "xform.rkt") and get a
stack trace?
My guess is that something goes wrong in communicating with the
subprocess that created by "xform.rkt" to run the C preprocessor, and
we should be able t
I have not had a lot of experience building Racket from source, but I
downloaded the minimal racket source and followed the instructions on the
readme. The configure step seems to encounter no problems, but when I run
make afterwards, it gets to the step of "Compiling xform support... Done
making x
4 matches
Mail list logo
