[Self-interest] Self not working on x64 Linux

[Reinout Heeck]

On 10/09/2020 13:54, mayuresh at kathe.in wrote:
> For me, the Self system on being called as "./Self -s kitchen.snap" crashed with the output as below;
> Self VM fatal error (/opt/self/vm/src/any/memory/generation.cpp, line 351): Couldn't allocate old space contiguous with new space

Let us first verify the integrity of your *.snap files by comparing your 
sha1sum outputs with the below (they should be exactly the same):

$ sha1sum *
1ab4e4f0a10ecbe5309094504da846f7cdab5039  core.snap
sha1sum: handbook: Is a directory
4a42091c9882f1e1d22a0e7fe7e57e98f2ff4612  kitchensink.snap
3e2cd2bccb0b5a398df0e8fb84a6b0aa2e5a437f  morphic.snap
8a5458f0171a295cae9f0c0a9a7a68fd4208bea0  Self
b17c34e03c6645844940683989a3bf80fa7cad19  SelfHandbook.pdf

If those match then your problem is getting beyond my knowledge.


One last suggestion I have (given the kind of error message) is to try 
to turn memory layout randomization off, see

https://linux-audit.com/linux-aslr-and-kernelrandomize_va_space-setting/

but my hopes are low with that fix, because if that is the source of the 
problem I'd expect Self to fail on my system too...


-Reinout


>
> VM Version: 2017.1.13, Tue 16 May 17 00:45:42 Linux i386 (4.5.0-205-gd942ba2-dirty)
>
> Self process 6391 on ideapad-330s-14lkb-u has crashed.
> Do you want to:
> 1) Quit Self (optionally attempting to write a snapshot)
> 2) Try to print the Self stack
> 3) Try to return to the Self prompt
> 4) Force a core dump
> 5) Print the interrupted context registers
>
> Any ideas what might be wrong?
>
> On Thursday, September 10, 2020 05:00 PM IST, Reinout Heeck <reinz at desk.org> wrote:
>   
>> I tried it on our 64bit development container  (with X11+vnc server)
>> that is running under Docker under the MsWindows WSL2 Linux subsystem.
>>
>>
>> This system reports as follows:
>>
>> $ uname -a
>> Linux f466c95cd9ce 4.19.104-microsoft-standard #1 SMP Wed Feb 19
>> 06:37:35 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
>>
>> $ cat /etc/issue
>> Ubuntu 20.04.1 LTS \n \l
>>
>>
>> running Self Manadarin for the first time gave a library not found error:
>>
>> $ ./Self
>> ./Self: error while loading shared libraries: libXext.so.6: cannot open
>> shared object file: No such file or directory
>>
>> I installed the 32 bit version of the x extensions:
>>
>> $ sudo apt install libxext6:i386
>>
>>
>> thereafter Self starts and shows a morphic window!
>>
>> $./Self -s morphic.snap
>> for I386:  LogVMMessages = true
>> for I386:  PrintScriptName  = true
>> for I386:  Inline = true
>> for I386:  SICDeferUncommonBranches = false (not implemented)
>> for I386:  SICReplaceOnStack = false (not implemented)
>> for I386:  SaveOutgoingArgumentsOfPatchedFrames = true
>>
>>       Welcome to the Self system!  (2017.1/2)
>>
>> ...etc..
>>
>>
>> I don't know how this translates to Redhat...
>>
>> HTH,
>>
>> Reinout Heeck
>>
>>
>>
>> On 10/09/2020 12:24, mayuresh at kathe.in wrote:
>>> I tried Self "Mandarin" 2017.1 released May 2017 under a previously setup Ubuntu 64-bit system following instructions from Russell to install the 32-bit libraries required for the same.
>>> The environment failed to start-up and even Russell has confirmed the same.
>>> I am currently on a RHEL Workstation install and I don't know how to install the required 32-bit libraries under this environment, if someone could help me out, I would be really thankful.
>>>
>>> BTW, could others who are using a 64-bit GNU/Linux system try running the Self "Mandarin" 2017.1 release?
>>> The failure message is unfathomable to me.
>>>
>>> Thanks,
>>>
>>> ~Mayuresh
>>>
>>> _______________________________________________
>>> Self-interest mailing list
>>> Self-interest at lists.selflanguage.org
>>> http://lists.selflanguage.org/mailman/listinfo/self-interest
>> _______________________________________________
>> Self-interest mailing list
>> Self-interest at lists.selflanguage.org
>> http://lists.selflanguage.org/mailman/listinfo/self-interest