Project

General

Profile

Actions

Bug #21779

closed

Do not export functions from statically linked extensions

Bug #21779: Do not export functions from statically linked extensions

Added by nobu (Nobuyoshi Nakada) about 17 hours ago. Updated about 16 hours ago.

Status:
Closed
Assignee:
-
Target version:
-
[ruby-core:124187]

Description

Reported at https://github.com/ruby/io-console/pull/105.

This is caused by InitVM_console exposed from the statically linked io/console is called from the loaded io-console gem.
The static InitVM_console initializes the ractor local storage key, but it is different from the key used in the gem extension.

Also, the workaround for conflict between Init functions is necessary for InitVM functions too.

https://github.com/ruby/ruby/pull/15539

Updated by nobu (Nobuyoshi Nakada) about 17 hours ago Actions #1

  • Description updated (diff)

Updated by nobu (Nobuyoshi Nakada) about 16 hours ago Actions #2

  • Status changed from Open to Closed

Applied in changeset git|bc2a8a002a6c41fc1b28e02e15e2fb2b72d1b66e.


[Bug #21779] Uniquify InitVM functions as well as Init

Avoid possible name conflict when --with-static-linked-ext.

Actions

Also available in: PDF Atom