Skip to content

should libgap be fork(2)-safe? #6456

Description

@dimpase

We have a scenario where an application which uses libgap calls fork on itself. It appears to work, except in the case where the corresponding installation of GAP has Browse package installed. In this case fork call leads to a lock-up, involving libgap calling ncurses.so GAP kernel module from Browse, which in turns calls libncurses or its equvalent, and, oops, it all freezes. Hitting Ctrl-C produces a dump showing that just mentioned components involved. See e.g. gap-system/homebrew-gap#23 (comment)

As there is no Unload equivalent to LoadPackage, the most obvious workaround is not having Browse installed. Which is kind of silly. Should work be put into getting it fixed?

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind: bug: unexpected errorIssues describing bugs in which computation unexpectedly encounters an error, and PRs fixing them

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions