RB not running on later Linux distros

Trying to run RB on a newer Linux distribution will result in a memory access violation.
Using valgrind to debug the memory errors will result in a running RB server.

How could we get RB running on newer Linux distributions without the 20x slowdown due to valgrind debugging the memory errors?

Thanks in advance for any pointers.

hi,
are you using 64-Bit linux? If so RB will not work.It is designed to work on 32-bit Os.
For some 64 -bit linux versions by installing some special software you can make 32-bit applications like RB work on 64-bit OS.
another solution is install virtual box or vmware in your system then install 32-bit os and run RB.
you can transfer files through rsync.

Yeah, 64 bit Linux is a problem and sometimes you can load the 32 bit libraries and get it to work.

However, even modern 32 bit Linux releases will have problems running the Runbasic server.

Carl, we simply need a fresh Runbasic recompile using current Linux libraries for both 32 bit and 64 bit Liunx.

Yes, I use 64-bit Linux, but the modern distributions support cross architecture, since it would not be possible to even get it running using valgrind to debug the memory violation error.

I am also thinking, that we need a recompile with more recent libraries to get a working RB.

So I also tried to run RB on a later 32-bit distribution, but the same memory access violation is reported.
I have then searched the forum for "kernel" and found mention of support for Kernel 2.6 only, so we would really need an upgrade to Kernel 5.0 or higher.

OK, so the issue is really related to the supported kernel release.

I installed Debian 6.0 downloaded from cdimage.debian.org/cdimage/archive/6.0.10/multi-arch/iso-dvd/, since the v6 Debian repositories are no longer available on the net due to support being stopped in 2016.
Now RB runs without problems on the 32-bit distribution.

I am using kernel version 4.19.20. RB Server is working fine for me.
ibb.co/X2W9fN8

Ran it under WSL2, which uses Linux kernel 5.4.72, ran just fine.

Going to attempt it on my live Linux box, as well.


EDIT:

Running on my live server, which is Ubuntu LTS 20.04.2, with kernel version 5.4.0-77-generic, also runs without any memory errors.

The system RB is working on is:

Linux version 2.6.32-5-686 (Debian 2.6.32-48squeeze6) (jmm@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue May 13 16:33:32 UTC 2014

The system RB is not working on is:

System: Host: stefan-VirtualBox Kernel: 5.4.0-77-generic i686 bits: 32 compiler: gcc v: 7.5.0 
 Desktop: Cinnamon 4.4.8 wm: muffin dm: LightDM Distro: Linux Mint 19.3 Tricia 
 base: Ubuntu 18.04 bionic 

Interesting results, I moved and started RBP on my Ubuntu 18.04 WSL2 container, and on that, I get a segmentation fault when I try to start RB.

18.04 details:




Actually, even weirder, when I use the WSL2 Ubuntu 20.04 container on my main computer, I get a segmentation fault. On my Surface laptop, it runs fine.

Checking the library dependencies things seem to be the same.
System where RB is working:

ldd ./rbp | sort
	libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7457000)
	libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb76f5000)
	/lib/ld-linux.so.2 (0xb772c000)
	libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb75b2000)
	libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb7703000)
	librt.so.1 => /lib/i686/cmov/librt.so.1 (0xb76fa000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0xb75d8000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0xb743a000)
	libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb743d000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb7435000)
	libz.so.1 => /usr/lib/libz.so.1 (0xb759e000)
	linux-gate.so.1 => (0xb772b000)

System where RB is not working:

ldd ./rbp | sort
	libbsd.so.0 => /lib/i386-linux-gnu/libbsd.so.0 (0xb79f6000)
	libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb7a51000)
	libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb7ea2000)
	/lib/ld-linux.so.2 (0xb7ef2000)
	libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb7c4e000)
	libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb7eb3000)
	librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb7ea8000)
	libX11.so.6 => /lib/i386-linux-gnu/libX11.so.6 (0xb7d54000)
	libXau.so.6 => /lib/i386-linux-gnu/libXau.so.6 (0xb7a1e000)
	libxcb.so.1 => /lib/i386-linux-gnu/libxcb.so.1 (0xb7a23000)
	libXdmcp.so.6 => /lib/i386-linux-gnu/libXdmcp.so.6 (0xb7a17000)
	libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb7c2f000)
	linux-gate.so.1 (0xb7ef0000)

So the only difference seems to be libbsd?

I directly extract the RB ZIP file for Linux into my home folder, should be OK, since RB is not requesting any special location.
In my case I can only get RB running on a Linux release from the time RB was released.
My main system is Windows and I run any Linux through VirtualBox.
According to Chris he has problems based on the hardware, since he has the same Linux release installed on different hardware.

To be able to find the root cause of RB failing to run in some cases, we would need to compare the entire system information about working configurations and failing ones.
In my case, due to using VirualBox, the hardware is the same, since there is no difference in the VirtualBox guest configuration.

Chris Iverson would be able to find the difference between the hardware which causes RB to fail.

So I created a bash file to run valgrind with specific parameters:
#!/bin/bash

binName="rbp"
imageName="rb.im"

cd ~/rb101free/

valgrind -v --log-file=rbp_valgrind_%p.log --error-limit=no ./$binName $imageName

Chris Iverson , hope you don't mind using your lb5alpha start script as a blueprint ::)

The summary is as shown below:


Is anyone willing to run valgrind on a newer system where it does not fail with any error and post the summary here or give feedback about the valgrind log contents?