[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[MIT-Scheme-devel] Fedora Core 3
From: |
Matt Birkholz |
Subject: |
[MIT-Scheme-devel] Fedora Core 3 |
Date: |
Fri, 18 Mar 2005 04:50:44 +0000 |
> From: Vinay Menon <address@hidden>
> Date: Sun, 13 Mar 2005 01:16:14 +0530
>
> Im trying to get MIT Scheme running on my Fedora Core 3. It gives me a
> Segmentation fault.
Me too, on Debian Testing. I assume you, like me, pulled the HEAD CVS
revisions and tried to build from sources. I got a seg fault like
this:
>> A hardware fault has occurred within critical section "garbage collector
daemon".
>> [signal 11 (SIGSEGV), code 1]
>> Successful recovery is unlikely.
I eventually recalled that runtime.com contains microcode-specific
things like primitive-procedure offsets. My freshly-built microcode
has a Static_Primitive_Procedure_Table that does not match. When the
7.7.90 runtime.com says execute primitive #548 (vector-ref), and my
hacked microcode executes primitive #548 (vector-8b-set!) instead, I get
a mess as above.
> Also mentioned in the site is that I cant build it from the sources
> until I have a version running on my system. Anyone face the same
> problem, and have a fix ..
My fix, thus far, is to pull the CVS revisions tagged release-7-7-90
and build the microcode. That seems to work. Now I can build the
bintopsb for release-7-7-90. Together with the psbtobin for my hacked
microcode, I hope to translate the runtime .bin files (syntaxed by
release-7-7-90) into .bins that will match my spiffy new microcode...
and eventually have an interpreted-code-only runtime.com for my new
microcode... pant, pant...
The rest of the bootstrap process is left as an exercise...
I would love to hear how Chris bootstraps bands for a new microcode.
While skimming bintopsb.c I noticed options called "allow_cc" and
"allow_bands". Maybe I can translate a compiled runtime.com...