Skip to content

add disallowing start fn as a config option#2

Open
pwang200 wants to merge 1 commit into
1.0.9from
1.0.9_disallow_start
Open

add disallowing start fn as a config option#2
pwang200 wants to merge 1 commit into
1.0.9from
1.0.9_disallow_start

Conversation

@pwang200

@pwang200 pwang200 commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@pwang200 pwang200 force-pushed the 1.0.9_disallow_start branch from 48e7a0f to 6c58d8b Compare July 9, 2026 19:13
WASMI_CONFIG_PROP(void, ignore_custom_sections, bool)

/**
* \brief Whether or not Wasm modules that declare a `start` function are allowed.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the motivation behind this config flag? Maybe something like this:

Wasm's start function executes automatically when a module is instantiated, before any explicit entry 
point is called. This PR closes a potential execution gap by letting the embedder reject any module that 
declares a start function outright, rather than allowing it to run code the instant it's loaded.
  1. If that's accurate, can you update the PR description?
  2. Is this something that should be proposed in the upstream project?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants