Stream: git-wasmtime

Topic: wasmtime / Issue #537 Debug a wasm application with reaso...

Wasmtime GitHub notifications bot (Mar 11 2020 at 15:39):

yurydelendik edited Issue #537:

I'm trying to run a large (~15 MB) wasm application that crashes on ud2. Is there any way to determine which function the crash address corresponds to?

Wasmtime GitHub notifications bot (Mar 11 2020 at 15:42):

whitequark commented on Issue #537:

@yurydelendik Are the build instructions here sufficient?

Wasmtime GitHub notifications bot (Mar 11 2020 at 20:46):

yurydelendik commented on Issue #537:

@whitequark it was not trivial but I was able to produce "yosys.wasm".

I added another commit to #1260. With this PR, per Activity Monitor and Instruments on my computer, the DWARF transform does not take more than 50 sec and memory is not growing past 2.4Gb. If you have time, can you confirm that it is the case on your side?

Wasmtime GitHub notifications bot (Mar 15 2020 at 03:16):

whitequark commented on Issue #537:

I greatly appreciate your work here. Unfortunately right now I'm not in a position to reproduce those results for personal reasons. The numbers you mention seem like they would allow me to proceed with my original work on wasm-ing Yosys; I won't get around to that for a while, so I'm closing the issue, because it seems like you've pretty much solved it. I'll make sure to report my results once I get around to it.

Wasmtime GitHub notifications bot (Mar 15 2020 at 03:16):

whitequark closed Issue #537:

I'm trying to run a large (~15 MB) wasm application that crashes on ud2. Is there any way to determine which function the crash address corresponds to?

Wasmtime GitHub notifications bot (Apr 25 2020 at 00:22):

whitequark commented on Issue #537:

@yurydelendik I just got around reproducing these results. Unfortunately, it seems that I hit a snag; on freshly compiled Yosys with WASI SDK 10, I get this if I pass -g after something like a minute of high CPU load:

Error: failed to run main module `yosys.wasm`

Caused by:
    0: Debug information error
    1: Hit the end of input before it was expected

Here's the problematic wasm file.

However, I'd like to say that even if you never fix this, y'all are still totally awesome. That's because I don't need debug information anymore! Almost everything in Yosys (except for a bizarre argv-related bug I have no idea what to make of) that I tested so far not only works perfectly well, but also with amazingly low startup latency and incredible speed.

Last updated: Oct 23 2024 at 20:03 UTC