search

spitbol / x64

SPITBOL x64 provides raw power and speed for non-numeric computation on the x86_64 architecture
GNU General Public License v3.0
256 stars 23 forks source link

Running any .spl file always results in segfault #18

Closed EvanSandersd closed 1 year ago

EvanSandersd commented 1 year ago

Downloaded the 64x version of SPITBOL using Debian 11 Linux, arm64.

Instructions included in the README also does not seem to align with the instructions on the GITHUB. Regardless, after following the README, it still produces unexpected results.

The file location is "usr/local/bin/spitbol". Inputting the command "$spitbol [file name]" in the native terminal does not produce expected results under any circumstances. It will always produce a segfault, even after chmod +755 following a successful build (as defined in the instructions in the README included).

Attempts at opening any .spl, .sno, or .spx file results in segfault.

Typing in the command "$spitbol" produces expected results as defined in the README, displaying the version number (v4.0) along with the various built-in shortcut commands.

Attempts at running the "sanity-check" included in the SPITBOL file always results in segfault.

Debian 11 is capable of running .sno files when using SNOBOL5.

CheyenneWills commented 1 year ago

Am I correct in assuming that you downloaded the tar.gz or .zip file from the Releases link and did not download/build from source?

EvanSandersd commented 1 year ago

Yes, you are correct.

CheyenneWills commented 1 year ago

I have updated the tar.,gz / zip files to release V4.0a which should contain the fix for this problem.

CheyenneWills commented 1 year ago

I've pushed a new development branch that has some improvements.

Once it has been tested, I will be promoting that branch to the main branch.

CheyenneWills commented 1 year ago

This issue is a dup of #11