SERVER-138398In Code Review
In-process-derived stack traces are mis-symbolized due to BOLT rewriting
Stack traces all in crashes, asserts, and the heap profiler are mis-symbolized due to BOLT. Frames will resolve to unrelated data symbols and wrong function names. The bug is that both abseil and libunwind assume a load relocation for program counters that is now incorrect due to BOLT adding a second {{LOAD}} segment. Both abseil and libunwind assume that the first load segment is the only load segment, and look up symbol names relative to that segment. The impact is that emitted stack traces