Wasmtime GitHub notifications bot (Jul 13 2023 at 15:09): Wasmtime GitHub notifications bot (Jul 13 2023 at 15:09):jameysharp commented on issue #6720:
Thank you! After your previous PR, @michelledaviest and @cfallin were recently trying out Samply with Wasmtime on macOS and we ran into issues, so I'm hoping this will help. I don't remember what the issues were though; Michelle and Chris, could you take a look at these instructions and see if they help you?
Wasmtime GitHub notifications bot (Jul 13 2023 at 17:26):michelledaviest commented on issue #6720:
Hi! Our specific issue was that while samply works with perfmaps in wasmtime, the call tree and flamegraph that comes up only allows you to expand host code to show native code. The guest code function addresses don't get symbol names associated with them and can't be expanded into native code, so you can't actually inspect any of the guest code. Regardless, these instructions are exactly how I ran samply with perfmaps.
Wasmtime GitHub notifications bot (Jul 17 2023 at 09:45):Maaarcocr commented on issue #6720:
Hi! Our specific issue was that while samply works with perfmaps in wasmtime, the call tree and flamegraph that comes up only allows you to expand host code to show native code. The guest code function addresses don't get symbol names associated with them and can't be expanded into native code, so you can't actually inspect any of the guest code. Regardless, these instructions are exactly how I ran samply with perfmaps.
I think the issue may be that I was running a version of samply built from source, which has support for perfmaps. I think the latest release on crates.io may not do so, which leads to not seeing guest code symbolised. I'll make sure to adjust the docs to outline this. This may change in the future when samply releases a new version.
Last updated: Dec 23 2024 at 13:07 UTC