Path: utzoo!attcan!uunet!mcsun!ukc!edcastle!lfcs!nick From: nick@lfcs.ed.ac.uk (Nick Rothwell) Newsgroups: comp.lang.functional Subject: Re: help request on edml installation Keywords: Edinburgh SML, Apollo, installation Message-ID: <5301@castle.ed.ac.uk> Date: 25 Jul 90 09:29:31 GMT References: <1990Jul24.114932.6727@forwiss.uni-passau.de> Reply-To: nick@lfcs.ed.ac.uk (Nick Rothwell) Organization: Wavetables 'R' Us Lines: 28 In-reply-to: grass@unipas.fmi.uni-passau.de (Grass) In article <1990Jul24.114932.6727@forwiss.uni-passau.de>, grass@unipas (Grass) writes: >Has anybody successfully ported Edinburgh SML to Apollo (SR 9.7 software) ? Apollo's are horrible. We spent a week battling with the software when doing the initial EdML port. >Our problem is the following: starting SML in its raw state from >smlcore.exp.backup (step 3 in the README instructions) crashes immediately >with the message "Memory fault". >Invoking the program explicitly (by typing: > /fam.src/fam -h 2000 smlcore.exp.backup smlcore.exp >) seems to work, but any simple input (e.g. - 3+2;) crashes with an access >violation in routine "RunState" at line 547. My first guess: bugs in the C compiler. I've often had to simplify expressions in the EdML interpreter to get correct behaviour. The other thing to check is all the byte-sex flags and so on in the configuration header file, but since it's getting as far as relocating the heap and giving you a prompt, I doubt this is wrong. >Wolf-Dieter Tiedemann Nick. -- Nick Rothwell, Laboratory for Foundations of Computer Science, Edinburgh. nick@lfcs.ed.ac.uk !mcsun!ukc!lfcs!nick ~ ~~ ~~ ~~ ~~ Hey, son, get that DeLorean off the track! And ~~ ~~ ~~ ~~ ~ what have you done with all my lovely harpsichords?