Portability problem
Nobody has claimed this yet.
- Dominant language
- Gleam
- Stars
- 121
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I am not sure if I do something wrong (probably), but I run into this problem:
root@buster:~# gitscan
=ERROR REPORT==== 17-Jul-2025::14:26:28.084149 ===
beam/beam_load.c(150): Error loading module gleescript_main_shim:
corrupt atom table
escript: exception error: undefined function gleescript_main_shim:main/1
in function escript:run/2 (escript.erl, line 904)
in call from escript:start/1 (escript.erl, line 418)
in call from init:start_it/1
in call from init:start_em/1
in call from init:do_boot/3
root@buster:~# erl
Erlang/OTP 27 [erts-15.2.7] [source] [64-bit] [smp:6:6] [ds:6:6:10] [async-threads:1] [jit:ns]
Eshell V15.2.7 (press Ctrl+G to abort, type help(). for help)
This is a Debian buster machine (yeah, it is EOL 2022, but it exists nonetheless) where I installed esl-erlang_27.3.4-1~debian~buster_amd64.deb. The Erlang shell works and shows OTP 27. I was of the impression that this should work.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the gitscan escript failure on Debian buster with the reported Erlang/OTP 27 package, then compare it with a working environment. The issue names no repository file or test; done means identifying and fixing the portability cause so gitscan starts without the corrupt atom table error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100