Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Error Running Example Code

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell, python
Domain
backend

Research direction

Start by reproducing python program.py in the reported WSL setup, then inspect program.py line 5 and the compiled libffi-example.so alongside the GHC library versions named in the traceback. Done means the example loads successfully without the stg_gc_unpt_r1 undefined-symbol error.

Written by the indexing model from the issue text.

Description

I managed to get to the point of successfully compiled the example code. Then I get to running the example with 'python program.py' and I get an error:

Traceback (most recent call last):
  File "program.py", line 5, in <module>
    lib = cdll.LoadLibrary("./libffi-example.so")
  File "/usr/lib/python2.7/ctypes/__init__.py", line 444, in LoadLibrary
    return self._dlltype(name)
  File "/usr/lib/python2.7/ctypes/__init__.py", line 366, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /usr/lib/ghc/ghc-prim-0.5.2.0/libHSghc-prim-0.5.2.0-ghc8.4.4.so: undefined symbol: stg_gc_unpt_r1

I'm not sure what stg_gc_unpt_r1 is, and what to do about it. I do not have a tonne of expereince with python, but have to do some work with it and I want to get this example working.
I compiled everything on WSL because windows does not support dynamic linking. If there is any information that could help me, that would be great.

Dominant language
Haskell
Stars
58
Forks
6
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.