David,
RC2 is working fine for ProofPower. I am testing on Snow Leopard using SVN rev 924 of the Poly/ML source. I tried both x86_64 and i386 architectures - to get the latter work you still seem to have to specify CXXFLAGS etc. I see that configure is still using xmkmf to test for X windows and therefore not finding it.
However while hamlet compiles and runs OK with poly compiled for the 32 bit architecture, it compiles but fails with a bus error with the 64 bit architecture. I believe I configured the Makefile correctly - I adjusted the settings for POLY_LIBDIR and added the appropriate -arch option to the step where it links the executable. I've appended the output from the dynamic linker and gdb:
I am afraid I don't have a cutdown version of the problem, because there isn't really anything to cut down: it appears to be failing before calling the hamlet main function.
Regards,
Rob.
rda]- DYLD_PRINT_LIBRARIES= hamlet dyld: loaded: /Users/rda/bld/hamlet-1.3.1/./hamlet dyld: loaded: /usr/local/poly/x86_64/lib/libpolyml.1.dylib dyld: loaded: /usr/lib/libstdc++.6.dylib dyld: loaded: /usr/lib/libSystem.B.dylib dyld: loaded: /usr/lib/system/libmathCommon.A.dylib Bus error rda]- gdb hamlet GNU gdb 6.3.50-20050815 (Apple version gdb-1344) (Fri Jul 3 01:19:56 UTC 2009) Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared libraries .... done
(gdb) run Starting program: /Users/rda/bld/hamlet-1.3.1/hamlet Reading symbols for shared libraries +++. done
Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x00000001000060f0 [Switching to process 18897] 0x00000001000060f0 in PolyML.runFunction(1)(1) () (gdb) where #0 0x00000001000060f0 in PolyML.runFunction(1)(1) () #1 0x000000018298a968 in ?? () Previous frame inner to this frame (gdb could not unwind past this frame) (gdb)
Rob, Rob Arthan wrote:
RC2 is working fine for ProofPower. I am testing on Snow Leopard using SVN rev 924 of the Poly/ML source. I tried both x86_64 and i386 architectures - to get the latter work you still seem to have to specify CXXFLAGS etc. I see that configure is still using xmkmf to test for X windows and therefore not finding it.
I think any change here needs to wait for updates to autoconf. I'd prefer not to put any special tests in myself.
However while hamlet compiles and runs OK with poly compiled for the 32 bit architecture, it compiles but fails with a bus error with the 64 bit architecture. I believe I configured the Makefile correctly - I adjusted the settings for POLY_LIBDIR and added the appropriate -arch option to the step where it links the executable. I've appended the output from the dynamic linker and gdb:
rda]- DYLD_PRINT_LIBRARIES= hamlet dyld: loaded: /Users/rda/bld/hamlet-1.3.1/./hamlet dyld: loaded: /usr/local/poly/x86_64/lib/libpolyml.1.dylib dyld: loaded: /usr/lib/libstdc++.6.dylib dyld: loaded: /usr/lib/libSystem.B.dylib dyld: loaded: /usr/lib/system/libmathCommon.A.dylib Bus error
This is on Mac OS X. I think you probably missed off the -segprot POLY rwx rwx from the link step. Try that and see if it fixes the problem. It builds and runs fine on 64-bit Linux.
I think once 5.3 is released I'll have a go at separating out the code from the mutable data when exporting and then it will be possible to use the conventional "text" (execute-read) and "data" (read-write) segments. That isn't possible at the moment because profiling, at least, writes into the code segments.
Regards, David
David,
On Monday 02 Nov 2009 11:35 am, David Matthews wrote:
Rob,
Rob Arthan wrote:
RC2 is working fine for ProofPower. I am testing on Snow Leopard using SVN rev 924 of the Poly/ML source. I tried both x86_64 and i386 architectures - to get the latter work you still seem to have to specify CXXFLAGS etc. I see that configure is still using xmkmf to test for X windows and therefore not finding it.
I think any change here needs to wait for updates to autoconf. I'd prefer not to put any special tests in myself.
That's fine by me - I don't need the X bindings at the moment and I am sure it would be easy to work around the problem if I did.
However while hamlet compiles and runs OK with poly compiled for the 32 bit architecture, it compiles but fails with a bus error with the 64 bit architecture. I believe I configured the Makefile correctly - I adjusted the settings for POLY_LIBDIR and added the appropriate -arch option to the step where it links the executable. I've appended the output from the dynamic linker and gdb:
rda]- DYLD_PRINT_LIBRARIES= hamlet dyld: loaded: /Users/rda/bld/hamlet-1.3.1/./hamlet dyld: loaded: /usr/local/poly/x86_64/lib/libpolyml.1.dylib dyld: loaded: /usr/lib/libstdc++.6.dylib dyld: loaded: /usr/lib/libSystem.B.dylib dyld: loaded: /usr/lib/system/libmathCommon.A.dylib Bus error
This is on Mac OS X. I think you probably missed off the -segprot POLY rwx rwx from the link step. Try that and see if it fixes the problem. It builds and runs fine on 64-bit Linux.
Yes, that fixes it. I was forgetting that missing this off causes a runtime error rather than a linktime error.
I think once 5.3 is released I'll have a go at separating out the code from the mutable data when exporting and then it will be possible to use the conventional "text" (execute-read) and "data" (read-write) segments. That isn't possible at the moment because profiling, at least, writes into the code segments.
I guess that would be a good idea in the long term: one less thing for users to remember and (presumably) a little bit of extra protection for people using the C interface.
Thanks,
Rob.
Regards, David _______________________________________________ polyml mailing list polyml@inf.ed.ac.uk http://lists.inf.ed.ac.uk/mailman/listinfo/polyml
Rob,
Rob Arthan wrote:
RC2 is working fine for ProofPower. I am testing on Snow Leopard using SVN rev 924 of the Poly/ML source. I tried both x86_64 and i386 architectures - to get the latter work you still seem to have to specify CXXFLAGS etc. I see that configure is still using xmkmf to test for X windows and therefore not finding it.
I think any change here needs to wait for updates to autoconf. I'd prefer not to put any special tests in myself.
That's fine by me - I don't need the X bindings at the moment and I am sure it would be easy to work around the problem if I did.
Assuming that you have the Motif libraries installed as well as the other X libraries you ought to be able to compile it in by giving the appropriate paths: ./configure --with-x --x-includes=/usr/X11R6/include \ --x-libraries=/usr/X11R6/lib
Don't forget configure no longer compiles in X-Windows by default. You have to give the --with-x option explicitly.
Regards, David
-
David.Matthews＠prolingua.co.uk -
rda＠lemma-one.com