__main_argc_argv` called before runtime initialization

[キャロウ マーク]

When I try to load the .html for my compiled app under the debugger in Firefox I get a runtime exception:

native function `__main_argc_argv` called before runtime initialization

If I run without the debugger, the app runs.

I am using Emscripten’s default generated .html. Here are my Emscripten link options:

--source-map-base ./
--exclude-file '${PROJECT_SOURCE_DIR}/tests/testimages/cubemap*'
-s ALLOW_MEMORY_GROWTH=1
-s DISABLE_EXCEPTION_CATCHING=0
-s USE_SDL=2
-s USE_WEBGL2=1

plus a few —preload-file options for some image files.

Any idea why this is happening and how to fix it?

Regards

-Mark

[Alon Zakai]

That is very strange. Based on those link flags, you did not modify how the application starts up, so I have no idea how it could break like that. If it only happens in the Firefox debugger then perhaps it is a Firefox debugger bug somehow? That seems unlikely too. But maybe try debuggers in other browsers and other versions of Firefox (in particular I would try Firefox Nightly).

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/A5D9183C-ABB3-4D89-81DC-3DB38CFD6600%40callow.im.

[Sam Clegg]

When you have the debugger attached and you hit that error/assertion, what does the stack trace look like?

To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpThe1LhSJ%3DmiVjnyBc%3DHCYF7P7V-yKac1kYZ47arrztzA%40mail.gmail.com.

[キャロウ マーク]

> On Apr 16, 2024, at 5:15, 'Sam Clegg' via emscripten-discuss <emscripte...@googlegroups.com> wrote:
>
> When you have the debugger attached and you hit that error/assertion, what does the stack trace look like?
>

The debugger does not show a stack trace.

[Sam Clegg]

Can you click on the little red arrow next to the "Aborted" message in the console?  It should show the stack trace.

If not, can you set a break point in the `abort` function in the JavaScript file?  That should certainly give you a backtrace when you hit it.

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/4C7952F6-F8CF-4335-BDA5-2E740E925D8A%40callow.im.

Regards

    -Mark

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/4C7952F6-F8CF-4335-BDA5-2E740E925D8A%40callow.im.

[キャロウ マーク]

On Apr 16, 2024, at 12:39, 'Sam Clegg' via emscripten-discuss <emscripte...@googlegroups.com> wrote:

 

Can you click on the little red arrow next to the "Aborted" message in the console?  It should show the stack trace.

Aborted(Assertion failed: native function `__main_argc_argv` called before runtime initialization) es3loadtests.js:789:6

    abort http://127.0.0.1:8080/es3loadtests.js:789

    assert http://127.0.0.1:8080/es3loadtests.js:522

    createExportWrapper http://127.0.0.1:8080/es3loadtests.js:836

    <anonymous> debugger eval code:1

Here is the createExportWrapper function with the assert that is firing

function createExportWrapper(name, nargs) {

  return (...args) => {

    assert(runtimeInitialized, `native function \`${name}\` called before runtime initialization`);

    var f = wasmExports[name];

    assert(f, `exported native function \`${name}\` not found`);

    // Only assert for too many arguments. Too few can be valid since the missing arguments will be zero filled.

    assert(args.length <= nargs, `native function \`${name}\` called with ${args.length} args but expects ${nargs}`);

    return f(...args);

  };

}

This is only happening when the code is compiled -O0, -g. When compiled -O3 the app runs with the debugger open.

Regards

    -Mark

[Sam Clegg]

It makes sense that this would only happen in debug build since these checks (the ones performed by 

createExportWrapper) are only included in debug builds.

I still can't seem to see how `__main_argc_argv` is being called.  The `debugger eval code` might be a clue.. are you typing something into the DevTools to trigger this?

I assume your main function is just being called in the normal way that emscripten does.  e.g. via run -> doRun -> callMain -> wasmExports[`__main_argc_argv`]?  or are you calling main some other way?

Can you try setting a break point in `callMain` perhaps?    Do you hit that before the error you see?

--
You received this message because you are subscribed to the Google Groups "emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to emscripten-disc...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/9A4B06C8-CFB9-4161-A378-B1EB50FA7278%40callow.im.