From: SourceForge.net <no...@so...> - 2004-05-18 16:07:40
|
Bugs item #931071, was opened at 2004-04-07 13:42 Message generated for change (Comment added) made by dwarren You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101176&aid=931071&group_id=1176 Category: Other Group: Other Status: Open Resolution: None Priority: 5 Submitted By: John D. Ramsdell (ramsdell) Assigned to: Nobody/Anonymous (nobody) Summary: XSB 2.6 build fails on Fedora Core 1 Initial Comment: Something goes wrong when building cmplib. See the enclosed transcript. John ---------------------------------------------------------------------- >Comment By: David S. Warren (dwarren) Date: 2004-05-18 16:07 Message: Logged In: YES user_id=13069 Bart tells me that the problem is the fact that your Linux allocates virtual memory above a gigabyte, i.e. uses the top 2 bits of an address word in a valid address. XSB, by default, steals those bits for tagging. So that is probably the problem. XSB does have the capability of stealing other bits of an address word for tagging, but it does require some. That is done by choosing the correct macros (or defining your own new ones) in emu/cell_xsb.h. The macros that need defining are: enc_int, dec_int, enc_addr, dec_addr. You can see examples there. Those are old examples, and we now need 1 fewer bit, and integers should be handled OK since they now use a boxed representation for integers that can't be tagged. (Actually, do you get the BIG_MEM tagging? That seems to need only 1 bit at the top.) It looks like the default tagging takes the top 3 bits, but big_mem takes the bottom 2 (which are always 0, due to alignment), and then only the top one. Try defining BIG_MEM to get those macros and see what happens. -David ---------------------------------------------------------------------- Comment By: Alex Butler (fishman631) Date: 2004-05-18 15:30 Message: Logged In: YES user_id=294052 I am seeing the same problem on RedHat Enterprise 3 $ uname -r 2.4.21-15.ELsmp ----------------------------- echo 'mc(useinfer, [sysmod,optimize,spec_repr,quit_on_error]).' >> cmd... echo 'mc(varproc, [sysmod,optimize,spec_repr,quit_on_error]).' >> cmd... echo 'mc(writeasm, [sysmod,optimize,spec_repr,quit_on_error]).' >> cmd... /home/abutler/src/apps/xsb-2.6/bin/xsb -e "segfault_handler(warn)." < cmd... ++Memory violation occurred during evaluation. ++Please report this problem using the XSB bug tracking system accessible from ++ http://sourceforge.net/projects/xsb ++Please supply the steps necessary to reproduce the bug. Exiting XSB abnormally... make[2]: *** [all] Error 1 make[2]: Leaving directory `/export/woodstown1/abutler/src/Linux/xsb-2.6/cmplib' make[1]: *** [cmplib] Error 2 make[1]: Leaving directory `/export/woodstown1/abutler/src/Linux/xsb-2.6' make: *** [remake_dot_O_files] Error 2 ---------------------------------------------------------------------- Comment By: David S. Warren (dwarren) Date: 2004-05-07 14:08 Message: Logged In: YES user_id=13069 So the failure to compile the XSB compiler is the first error seen in the log. If you just try to run the xsb executable, do you get the same memory violation? (Compiling the compiler is not strictly necessary, but it should work.) I suspect that you do. That means that the compilation of the XSB executable must not have worked. Look carefully through that (C) compilation log and see if anything looks amiss. If all that is OK, then the only other thing that comes to mind is a problem we used to have with some systems, and that concerns the bits that XSB steals from addresses for tagging. Do you know where in the virtual address space that Fedora allocates memory. If it is above a gigabyte, that might be causing the problem. (It's easier for me if we correspond by email: wa...@cs...) -David ---------------------------------------------------------------------- Comment By: Bob Gustafson (bobgus) Date: 2004-05-07 01:43 Message: Logged In: YES user_id=462564 I have the same problem with build on: Fedora Core2(Test3) (w/selinux loaded, but enforce=0) ----------------------------------- echo 'mc(varproc, [sysmod,optimize,spec_repr,quit_on_error]).' >> cmd... echo 'mc(writeasm, [sysmod,optimize,spec_repr,quit_on_error]).' >> cmd... /usr/local/src/sel/XSB/bin/xsb -e "segfault_handler(warn)." < cmd... ++Memory violation occurred during evaluation. ++Please report this problem using the XSB bug tracking system accessible from ++ http://sourceforge.net/projects/xsb ++Please supply the steps necessary to reproduce the bug. Exiting XSB abnormally... make[2]: *** [all] Error 1 make[2]: Leaving directory `/usr/local/src/sel/XSB/cmplib' make[1]: *** [cmplib] Error 2 make[1]: Leaving directory `/usr/local/src/sel/XSB' make: *** [remake_dot_O_files] Error 2 [root@hoho2 build]# ---------------------------------------------------------------------- Comment By: Bob Gustafson (bobgus) Date: 2004-05-07 01:43 Message: Logged In: YES user_id=462564 I have the same problem with build on: Fedora Core2(Test3) (w/selinux loaded, but enforce=0) ----------------------------------- echo 'mc(varproc, [sysmod,optimize,spec_repr,quit_on_error]).' >> cmd... echo 'mc(writeasm, [sysmod,optimize,spec_repr,quit_on_error]).' >> cmd... /usr/local/src/sel/XSB/bin/xsb -e "segfault_handler(warn)." < cmd... ++Memory violation occurred during evaluation. ++Please report this problem using the XSB bug tracking system accessible from ++ http://sourceforge.net/projects/xsb ++Please supply the steps necessary to reproduce the bug. Exiting XSB abnormally... make[2]: *** [all] Error 1 make[2]: Leaving directory `/usr/local/src/sel/XSB/cmplib' make[1]: *** [cmplib] Error 2 make[1]: Leaving directory `/usr/local/src/sel/XSB' make: *** [remake_dot_O_files] Error 2 [root@hoho2 build]# ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=101176&aid=931071&group_id=1176 |