Skip to content

How to get a call stack when wasm-ctor-eval stops? #7255

@rdb

Description

@rdb

Hello,

Apologies if this is already documented somewhere, but I was unable to find it. I'm trying to find out how I can easily find where a particular call to an import is being made when wasm-ctor-eval hits something it can't eval. I was hoping to find some debug option so that I could see something like a traceback.

At the moment I am manually searching through the wasm disassembly, which is quite a painstaking process given that this is a huge binary. Any suggestions for making this process easier would be very helpful.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions