Closed krzysiek6d closed 2 years ago
I would start by trying to profile a toy example - compile some small program and try to profile it and see if it crashes (it might be something your program does in a weird way, or it might be toolchain/system/libc/whetever incompatibility). I'd also try different versions of Bytehound and see if it crashes with all of them. Also try to set MEMORY_PROFILER_USE_SHADOW_STACK
to 0
and see if it crashes then.
Hi, I suggested this way of checking to my colleagues but did not get a feedback if it's working or not. Anyway thank you very much for this hints. I'm closing this issue since there is no reason to have it opened infinitely ;) Thanks!
Hi
During memory profiling with bytehound I encountered crash with bracktrace containing 2 entries:
this leads to
aarch64_trampoline.s from this revision revision 51003a4 is quite old IMO - but maybe you're aware of some bugs related to that part of code or give a hint how should I debug such issues?