> Since you didn't provide the error message, I don't know what the problem is. The address might be a heap address, yes. Have you tried using a debugger?
Sorry, it was really cryptic from my part. Im using the v8::internal::wasm::ErrorThrower together with wasm::SyncCompile and wasm::SyncInstantiate. The message will can be a LinkError or CompileError The error thrower returns the type of the error together with "map: <hex>" and at first i thought that the hex was a offset address for the equivalent produced turbofan machine code, and turned on the flags to see the disassembly for the wasm code.. but in my case it didnt match, so i remain wandering where this offset (i assume) points to? I know by playing with v8 internals that map is the foundation to js objects.. so maybe is pointing to a js object on v8 heap? Thanks, and i will try to devote more time reading some v8 internals to figure out better ways to approach debugging and understanding more the wasm runtime. -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
