3 ms·

I don't see why the "individually enabled" part is inherent to the design. The JITs could emit these files automatically, if they wanted to. But the main point

I don't see why the "individually enabled" part is inherent to the design. The JITs could emit these files automatically, if they wanted to. But the main point is that "inability to support unwinding of anything that isn't AOT compiled native code" is factually incorrect: as far as I know, frame pointers plus this "hack" is currently the only widely available way to do just that.

quotemstr 4y ago
No, they can't, because doing so would be a constant drag on performance for processes not being profiled. Plus, there's no provision for VA reuse for the trampolines, so as the set of described functions grows, so does the magic text file in /tmp.