Re: [Hol-info] Uncaught exception: Chr
Hi Mike, I have located some mails I sent in 2005 where exactly this error was reported under mosml. The problem apparently arose because lots of ML level identifiers (val f, val g...) were created, and some internal mosml limit was breached. To get around this problem, Peter Sestoft provided a patched version of mosml that was able to deal with many more identifiers. We then used this version of mosml on the NetSem project. Perhaps Peter can put these changes in the current release of mosml. Alternatively I can probably track down some instructions for patching a release of mosml to fix this problem. Hope this is relevant Tom 2008/10/14 Mike Gordon <[EMAIL PROTECTED]>: > > Does anyone recognise: > > ! Uncaught exception: > ! Chr > > as a symptom of some kind of running out of space? > > It arises when rebuilding examples/acl2/ml in newer versions of hol > (warning: this takes a long time before crashing). > > Mike > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > hol-info mailing list > hol-info@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hol-info > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ hol-info mailing list hol-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hol-info
Re: [Hol-info] Uncaught exception: Chr
This exception is probably not directly caused by running out of space. Chr is raised by Char.chr : int -> char when applied to an int that doesn't map to a char. Konrad. On Oct 14, 2008, at 3:33 AM, Mike Gordon wrote: > > Does anyone recognise: > > ! Uncaught exception: > ! Chr > > as a symptom of some kind of running out of space? > > It arises when rebuilding examples/acl2/ml in newer versions of hol > (warning: this takes a long time before crashing). > > Mike > > -- > --- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > hol-info mailing list > hol-info@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hol-info - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ hol-info mailing list hol-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hol-info
Re: [Hol-info] Uncaught exception: Chr
Hi Konrad and Mike, I used to see this error frequently when running MoscowML. With PolyML I haven't seen it yet. To me it seemed to arise fairly arbitrarily, the common factors were: (1) I had run HOL for a long time, and (2) Define had failed a number of times before the crash (I gave it bad inputs). The error is quite serious because it crashes HOL completely. I had to restart HOL whenever it printed: ! Uncaught exception: ! Chr This error is one of the main reasons I switched to PolyML. Magnus On 14/10/2008, Konrad Slind <[EMAIL PROTECTED]> wrote: > This exception is probably not directly caused by running out of > space. Chr is raised by > > Char.chr : int -> char > > when applied to an int that doesn't map to a char. > > > Konrad. > > > On Oct 14, 2008, at 3:33 AM, Mike Gordon wrote: > > > > > Does anyone recognise: > > > > ! Uncaught exception: > > ! Chr > > > > as a symptom of some kind of running out of space? > > > > It arises when rebuilding examples/acl2/ml in newer versions of hol > > (warning: this takes a long time before crashing). > > > > Mike > > > > -- > > --- > > This SF.Net email is sponsored by the Moblin Your Move Developer's > > challenge > > Build the coolest Linux based applications with Moblin SDK & win > > great prizes > > Grand prize is a trip for two to an Open Source event anywhere in > > the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > ___ > > hol-info mailing list > > hol-info@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/hol-info > > > - > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > ___ > hol-info mailing list > hol-info@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hol-info > - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ hol-info mailing list hol-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hol-info
Re: [Hol-info] Uncaught exception: Chr
Tom Ridge wrote: Hi Mike, I have located some mails I sent in 2005 where exactly this error was reported under mosml. The problem apparently arose because lots of ML level identifiers (val f, val g...) were created, and some internal mosml limit was breached. To get around this problem, Peter Sestoft provided a patched version of mosml that was able to deal with many more identifiers. We then used this version of mosml on the NetSem project. Perhaps Peter can put these changes in the current release of mosml. Alternatively I can probably track down some instructions for patching a release of mosml to fix this problem. The patch is in the attached file. You need to unpack this file in your mosml/src directory. I.e., change to that directory, do tar xvzf mosml-patch.tgz and then a complete rebuild of Moscow ML. Assuming your makefile is already set up correctly for your installation, something like make clean ; make world ; make install should do the trick. If you're running on Windows, you're probably out of luck, though there are Moscow ML instructions on installing from sources for Windows. (And we don't have HOL working on Poly/ML on Windows either.) Michael. mosml-patch.tgz Description: application/compressed - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/___ hol-info mailing list hol-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hol-info
Re: [Hol-info] Uncaught exception: Chr
I also see this bug happen when trying to build examples/acl2/ml. However,
this patch doesn't seem to build right on a Mac running OS X (10.4) with the
following gcc:
$ gcc --version
i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5367)
The Makefile.inc section that is uncommented is
# For Mac OS X 10.x.y (Intel or PowerPC), use:
#
CPP=/usr/bin/cpp -no-cpp-precomp -P -traditional -Dunix -Umsdos
STRIP=echo
LD=gcc
DYNLD=gcc -bundle -bundle_loader ${MOSMLHOME}/bin/camlrunm
On starting "make world", the build fails with the last lines being
cd mosmllib; make all
/usr/bin/cpp -no-cpp-precomp -P -traditional -Dunix -Umsdos Array.mlp >
Array.sml
../camlrunm ../mosmlcmp -stdlib ../mosmllib -P none -imptypes Vector.sig
buildrealmap: opcode = 255 at 2332
bad opcode
make[1]: *** [Vector.ui] Error 2
make: *** [world] Error 2
"make world" builds fine without the patch. Any suggestions?
Peter
On Tue, Oct 14, 2008 at 8:02 PM, Michael Norrish <
[EMAIL PROTECTED]> wrote:
> Tom Ridge wrote:
>
>> Hi Mike,
>>
>> I have located some mails I sent in 2005 where exactly this error was
>> reported under mosml. The problem apparently arose because lots of ML
>> level identifiers (val f, val g...) were created, and some internal
>> mosml limit was breached. To get around this problem, Peter Sestoft
>> provided a patched version of mosml that was able to deal with many
>> more identifiers. We then used this version of mosml on the NetSem
>> project.
>>
>> Perhaps Peter can put these changes in the current release of mosml.
>> Alternatively I can probably track down some instructions for patching
>> a release of mosml to fix this problem.
>>
>
> The patch is in the attached file. You need to unpack this file in
> your mosml/src directory. I.e., change to that directory, do
>
> tar xvzf mosml-patch.tgz
>
> and then a complete rebuild of Moscow ML. Assuming your makefile is
> already set up correctly for your installation, something like
>
> make clean ; make world ; make install
>
> should do the trick.
>
> If you're running on Windows, you're probably out of luck, though
> there are Moscow ML instructions on installing from sources for
> Windows. (And we don't have HOL working on Poly/ML on Windows
> either.)
>
> Michael.
>
--
"In Your majesty ride prosperously
because of truth, humility, and righteousness;
and Your right hand shall teach You awesome things." (Psalm 45:4)
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/___
hol-info mailing list
hol-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hol-info
Re: [Hol-info] Uncaught exception: Chr
Peter Vincent Homeier wrote: > I also see this bug happen when trying to build examples/acl2/ml. > However, this patch doesn't seem to build right on a Mac running OS X > (10.4) with the following gcc: Yes, I'm afraid the instructions in my post yesterday were far too casual (not to mention wrong!). I have Peter Sestoft's original here: -- 0. Make a backup of your old mosml installation 1. Before unpacking the attached, make a build of mosml 2.01: In mosml/src/ domake clean world 2. Unpack the attached: In mosml/src/ dotar xvfz mosml-patch.tgz 3. Recompile the compiler to generate the new bytecode: In mosml/src/compiler domake all 4. Promote the compiler: In mosml/src/compiler domv mosmllnk mosmlcmp .. (I believe mosmllnk is unchanged, but promote for good measure) 5. Generate new bytecode for libraries, compiler and lexer by recompiling: In mosml/src/mosmllib domake clean all In mosml/src/compiler domake clean all In mosml/src/lex do make clean all 6. Recompile the runtime: In mosml/src/runtime do make all 7. Promote the runtime, compiler and lexer: In mosml/src/runtime do mv camlrunm .. In mosml/src/compiler domv mosmllnk mosmlcmp .. In mosml/src/lex do mv mosmllex .. 8. Check that the top-level works: In mosml/src do camlrunm compiler/mosmltop -stdlib mosmllib and evaluate some expressions. 9. Rebuild everything to check that the system is stable: In mosml/src do make clean world Check that src/mosmlcmp = src/compiler/mosmlcmp src/mosmllnk = src/compiler/mosmllnk src/mosmllex = src/lex/mosmllex 10. Install In mosml/src do make install 11. Check that HOL builds. -- Best, Michael. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ ___ hol-info mailing list hol-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hol-info
Re: [Hol-info] Uncaught exception: Chr
It turns out that the instructions Peter Sestoft sent you were slightly incomplete. In particular, before the 'make all' in steps 3 and 6, one must 'touch' the new files so that the make recognizes these are new versions of the files. Crucially, in step 8, one should use './camlrunm' instead of 'camlrunm'; otherwise one would invoke the installed version and get a bus error, and may mistakenly think that the build went wrong in some inexplicable way, when it actually worked. Finally, when rebuilding HOL, make sure to first go through all of the subdirectories of tools and do either 'make clean' or 'Holmake clean' as appropriate, in order to clean out all the old object code produced by the prior version of mosml, and then do the normal 'mosml < tools/smart-configure.sml' followed by 'build cleanAll' and 'build' commands. May I suggest that these instructions be added to the HOL installation instructions at http://hol.sourceforge.net/InstallKananaskis.html? Here is the corrected version: -- 0. Make a backup of your old mosml installation 1. Before unpacking the attached, make a build of mosml 2.01: In mosml/src/ domake clean world 2. Unpack the attached: In mosml/src/ dotar xvfz mosml-patch.tgz 3. Recompile the compiler to generate the new bytecode: In mosml/src/compiler dotouch Patch.sml Reloc.sml make all 4. Promote the compiler: In mosml/src/compiler domv mosmllnk mosmlcmp .. (I believe mosmllnk is unchanged, but promote for good measure) 5. Generate new bytecode for libraries, compiler and lexer by recompiling: In mosml/src/mosmllib domake clean all In mosml/src/compiler domake clean all In mosml/src/lex do make clean all 6. Recompile the runtime: In mosml/src/runtime do touch expand.c fix_code.c interp.c make all 7. Promote the runtime, compiler and lexer: In mosml/src/runtime do mv camlrunm .. In mosml/src/compiler domv mosmllnk mosmlcmp .. In mosml/src/lex do mv mosmllex .. 8. Check that the top-level works: In mosml/src do ./camlrunm compiler/mosmltop -stdlib mosmllib and evaluate some expressions. 9. Rebuild everything to check that the system is stable: In mosml/src do make clean world Check that src/mosmlcmp = src/compiler/mosmlcmp src/mosmllnk = src/compiler/mosmllnk src/mosmllex = src/lex/mosmllex 10. Install In mosml/src do make install 11. Check that HOL builds. -- Cheers, Peter On Wed, Oct 15, 2008 at 8:19 PM, Michael Norrish wrote: > Peter Vincent Homeier wrote: > > I also see this bug happen when trying to build examples/acl2/ml. > > However, this patch doesn't seem to build right on a Mac running OS X > > (10.4) with the following gcc: > > Yes, I'm afraid the instructions in my post yesterday were far too > casual (not to mention wrong!). I have Peter Sestoft's original here: > > -- > 0. Make a backup of your old mosml installation > > 1. Before unpacking the attached, make a build of mosml 2.01: > > In mosml/src/ do make clean world > > 2. Unpack the attached: > > In mosml/src/ do tar xvfz mosml-patch.tgz > > 3. Recompile the compiler to generate the new bytecode: > > In mosml/src/compiler do make all > > 4. Promote the compiler: > > In mosml/src/compiler do mv mosmllnk mosmlcmp .. > > (I believe mosmllnk is unchanged, but promote for good measure) > > 5. Generate new bytecode for libraries, compiler and lexer by > recompiling: > > In mosml/src/mosmllib do make clean all > In mosml/src/compiler do make clean all > In mosml/src/lex do make clean all > > 6. Recompile the runtime: > > In mosml/src/runtime do make all > > 7. Promote the runtime, compiler and lexer: > > In mosml/src/runtime do mv camlrunm .. > In mosml/src/compiler do mv mosmllnk mosmlcmp .. > In mosml/src/lex do mv mosmllex .. > > 8. Check that the top-level works: > > In mosml/src do camlrunm compiler/mosmltop -stdlib mosmllib > > and evaluate some expressions. > > 9. Rebuild everything to check that the system is stable: > > In mosml/src do make clean world > > Check that src/mosmlcmp = src/compiler/mosmlcmp > src/mosmllnk = src/compiler/mosmllnk > src/mosmllex = src/lex/mosmllex > > 10. Install > > In mosml/src do make install > > 11. Check that HOL builds. > -- -- "In Your majesty ride prosperously because of truth, humility, and righteousness; and Your right hand shall teach You awesome thing
Re: [Hol-info] Uncaught exception: Chr
I tried this on a Macintosh running Mac OS X version 10.5.6 (Leopard), and the process failed in step 6, when doing "make all" in the runtime directory: MinasTirith:runtime palantir$ make all gcc -c -Dunix -O2 -fno-defer-pop -fomit-frame-pointer -DTHREADED -I/Users/palantir/sml/mosml/include -o interp.o interp.c gcc -c -Dunix -O2 -fno-defer-pop -fomit-frame-pointer -DTHREADED -I/Users/palantir/sml/mosml/include -o expand.o expand.c gcc -c -Dunix -O2 -fno-defer-pop -fomit-frame-pointer -DTHREADED -I/Users/palantir/sml/mosml/include -o fix_code.o fix_code.c sed -n -e '/\/\* ML \*\//s/.* \([a-zA-Z0-9_][a-zA-Z0-9_]*\) *(.*/\1/p' \ compare.c extern.c externcp.c floats.c gc_ctrl.c hash.c intern.c interncp.c interp.c ints.c io.c lexing.c meta.c parsing.c str.c sys.c mosml.c unix.c md5sum.c callback.c dynlib.c > primitives2 sh -c 'if cmp -s primitives primitives2; \ then rm primitives2; \ else mv primitives2 primitives; \ fi' gcc -o camlrunm prims.o interp.o expand.o misc.o stacks.o fix_code.o main.o fail.o signals.o freelist.o major_gc.o minor_gc.o memory.o alloc.o roots.o compare.o ints.o floats.o str.o io.o extern.o externcp.o intern.o interncp.o hash.o sys.o meta.o parsing.o lexing.o gc_ctrl.o mosml.o unix.o runtime.o md5sum.o callback.o dynlib.o -lm -L/Users/palantir/sml/mosml/lib -ldl /usr/bin/ld: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libm.dylib unknown flags (type) of section 6 (__TEXT,__literal16) in load command 0 /usr/bin/ld: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libdl.dylib unknown flags (type) of section 6 (__TEXT,__literal16) in load command 0 /usr/bin/ld: /usr/lib/gcc/i686-apple-darwin8/4.0.1/../../../libSystem.dylib unknown flags (type) of section 6 (__TEXT,__literal16) in load command 0 collect2: ld returned 1 exit status make: *** [camlrunm] Error 1 MinasTirith:runtime palantir$ gcc --version i686-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5363) . . . Does anyone have an idea that might help? Do I need a new version of gcc? Has anyone else had success performing this upgrade under Leopard? Thanks for helping. Peter On Fri, Apr 3, 2009 at 4:12 PM, Peter Vincent Homeier wrote: > It turns out that the instructions Peter Sestoft sent you were > slightly incomplete. > > In particular, before the 'make all' in steps 3 and 6, one must > 'touch' the new files so that the make recognizes these are new > versions of the files. Crucially, in step 8, one should use > './camlrunm' instead of 'camlrunm'; otherwise one would invoke the > installed version and get a bus error, and may mistakenly think that > the build went wrong in some inexplicable way, when it actually > worked. > > Finally, when rebuilding HOL, make sure to first go through all of the > subdirectories of tools and do either 'make clean' or 'Holmake clean' > as appropriate, in order to clean out all the old object code produced > by the prior version of mosml, and then do the normal 'mosml < > tools/smart-configure.sml' followed by 'build cleanAll' and 'build' > commands. > > May I suggest that these instructions be added to the HOL installation > instructions at http://hol.sourceforge.net/InstallKananaskis.html? > > Here is the corrected version: > > -- > 0. Make a backup of your old mosml installation > > 1. Before unpacking the attached, make a build of mosml 2.01: > > In mosml/src/ do make clean world > > 2. Unpack the attached: > > In mosml/src/ do tar xvfz mosml-patch.tgz > > 3. Recompile the compiler to generate the new bytecode: > > In mosml/src/compiler do touch Patch.sml Reloc.sml > make all > > 4. Promote the compiler: > > In mosml/src/compiler do mv mosmllnk mosmlcmp .. > > (I believe mosmllnk is unchanged, but promote for good measure) > > 5. Generate new bytecode for libraries, compiler and lexer by > recompiling: > > In mosml/src/mosmllib do make clean all > In mosml/src/compiler do make clean all > In mosml/src/lex do make clean all > > 6. Recompile the runtime: > > In mosml/src/runtime do touch expand.c fix_code.c interp.c > make all > > 7. Promote the runtime, compiler and lexer: > > In mosml/src/runtime do mv camlrunm .. > In mosml/src/compiler do mv mosmllnk mosmlcmp .. > In mosml/src/lex do mv mosmllex .. > > 8. Check that the top-level works: > > In mosml/src do ./camlrunm compiler/mosmltop -stdlib mosmllib > > and evaluate some expressions. > > 9. Rebuild everything to check that the system is stable: > > In mosml/src do make clean world > > Check that src/mosmlcmp = src/compiler/mosmlcmp > src/mosmllnk = src/compiler/mosmllnk > src/mosmllex = src/lex/mosmllex > > 10. Install > > In mosml/src do make install > > 11. Check that HOL builds. > -
Re: [Hol-info] Uncaught exception: Chr
Peter Vincent Homeier wrote: > I tried this on a Macintosh running Mac OS X version 10.5.6 (Leopard), > and the process failed in step 6, when doing "make all" in the runtime > directory: Hi Peter, I just did a fresh patch of the system, following the instructions you've updated, and it all worked perfectly. My details look similar to yours: $ uname -a Darwin vpn202-248.vpn.in.nicta.com.au 9.6.0 Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386 i386 i386 MacBookPro2,2 Darwin $ gcc --version i686-apple-darwin9-gcc-4.0.1 (GCC) 4.0.1 (Apple Inc. build 5465) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The situation with Moscow ML is not ideal at the moment. I'm hoping that there will be a fresh release soon. Alternatively, we might try to release a special HOL branch of our own. Of course, the Poly/ML implementation works well on the Mac, so you could always use that... Best, Michael. -- This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com ___ hol-info mailing list hol-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hol-info
