pforth segmentation fault

[bumper314]

pforth isn't behaving properly (confirmed on 3 devices):

• When run without arguments, pforth seg faults.
• When run with the -i argument, pfroth runs, but it's a highly stripped down (useless) environment.

I'm able to build the same commit of pforth on my Mac, and it works as expected.
Let me know if I can do more to help.

[stephengroat]

@bumper314 have you run pkg up to make sure that everything is up to date?

[its-pointless]

Well i don't know much about forth but did manage to compile gforth on device. If you could tell me the arch of your device (uname -m) i could use someone who does use forth for some testing?

[bumper314]

@stephengroat Yes, all up to date or freshly installed yesterday/today.

@its-pointless Just installed on a 4th device and pforth works, so here's the breakdown:

• Worked
  • LG VK815 (aarch64)
• Failed
  • Nexus 5 (armv71)
  • Nexus 6 (armv71)
  • Samsung Note Pro 12 (armv71)

Happy to test. I wasn't able to get the Docker dev env setup for testing, but I can try suggestions on-device.

[its-pointless]

/~https://github.com/its-pointless/its-pointless.github.io/raw/master/files/dists/termux/extras/binary-arm/gforth_0.7.3_arm.deb

/~https://github.com/its-pointless/its-pointless.github.io/raw/master/files/dists/termux/extras/binary-aarch64/gforth_0.7.3_aarch64.deb

[its-pointless]

i can get pforth to work on arm by compiling pforth on device. So at the very least that should work.

[bumper314]

I'm able to build the pforth source on device and it runs correctly, so perhaps their's an issue with the build script.

I'm unable to install the debs due to unresolvable dependencies, but those also appear to be gforth instead of pforth.

Any other thoughts as to why building natively works vs the package? Perhaps a cross-compiler issue?

[its-pointless]

oh i messed that up i will fix that now

[its-pointless]

regarding why it works built on device and not cross compiled?

could be one of many different reasons.
the compilers are not quite the same is one answer. The compilers we use on device are not ndk sources but upstream llvm. After looking at things cross compiling forth is a strange thing as well...

[its-pointless]

K solved this with pull request #1804

[fornwall]

The PR is now merged and the fixed package is available as an update - nice work!

[bumper314]

Confirmed fix on both 32 and 64-bit devices. Thanks!