Florian Schmidt

Hi, I'm currently a bit busy and might take a little bit to get back to you on that, but, in the meantime, can you give me some information about...

Thanks for the bug report! I see you're running a Linux VM, not a unikernel, and guessing from the name, an HVM one. Since the tool is primarily designed as...

So, after thinking about this: * This happens when uniprof assumes a stack with frame pointers, but the code whose stack is being walked was compiled with -fomit-frame-pointer (or doesn't...

Could you try commit fab6d1edf4c29dc545ae6bc7caf6f3875c4b7555? It should fix the bus error, and instead show warnings whenever it tries to walk a stack and ends up with invalid addresses.

The 0 effectively invalidates the printed stack trace, because it says "this trace occurred 0 times". The idea is that, since this stack walk didn't finish successfully, it's not trustworthy...

So it does seem to hit only two different stacks, I wonder whether those both happen to be framepointer-less?

Alright, then I'll have to dig deeper into the issue. Sounds like there might be some issue, maybe with translating the addresses, or traversing the stack correctly. The tool's really...