[Gsll-devel] Execution errors?
Liam Healy
lhealy at common-lisp.net
Sun Aug 16 02:02:33 UTC 2009
On Tue, Aug 11, 2009 at 1:12 PM, Jason Nielsen<jdn at math.carleton.ca> wrote:
> On Tue, 11 Aug 2009, Jason Nielsen wrote:
>>
>> I've just updated to the latest version of gsll and am getting execution
>> errors that I do not recall getting previously when running the test suite
>> (it has been however a bit of time since I git pulled). Here is the result:
>>
>> TOTAL: 1483 assertions passed, 1 failed, 9 execution errors.
>>
>> the execution errors are all of the form:
>>
>> SCALE: Unhandled memory fault at #x1B3BA55C.
>> VECTOR-SET-ALL: Unhandled memory fault at #xA7C1C475.
>> etc.
>>
>> I'm not sure if this is cause for concern as it doesn't seem to change the
>> results of my code... but memory fault warnings give make me a little
>> uncomfortable!
>>
>> I'm running Ubuntu 8.10 on an x86-64 machine with sbcl 1.30.
>>
>
> I've done a little digging and the execution errors only happy when I run
> the test suite with gsll built into the lisp image (using
> save-lisp-and-die). If I simply require the package and run the test
> suite the 9 execution errors do not occur.
>
> Cheers,
> Jason
Which is still an error, albeit a more subtle one; thanks for the update.
Evidently, save-lisp-and-die destroys something that I'm implicitly
assuming is preserved. If you can narrow it down it might be worth
pursuing with the SBCL wizards either on #lisp or on the sbcl-devel
mailing list.
Liam
More information about the gsll-devel
mailing list