Segfaults after one translation

Open
#105 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
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reproducing the failure with the shown apertium.Translator('spa','cat') example and two consecutive translate calls. Inspect the Translator entry point and its translation lifecycle; done means repeated translations complete without a segmentation fault across the packages described.

Written by the indexing model from the issue text.

Description

Using any packages (I've tried a few), it works at the first execution, but it fails when executing a second translation

>>> r = apertium.Translator('spa','cat')
>>> r.translate('buenos días')
'bon dia'
>>> r.translate('buenos días')
Violació de segment (s'ha bolcat la memòria)
Dominant language
Python
Stars
35
Forks
27
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from apertium/apertium-python

All issues in apertium/apertium-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.