Ive been looking at the performance of a large-ish rust project at $company and it seems almost 50% of running time is spent in
strerror_l calls. Confusingly, the call graph generated by google’s pprof seems to indicate that a number of seemingly unrelated functions are spending a decent amount of time there.
Im wondering if anyone has encountered this issue or knows what actually calls
strerror_l under the hood.
Ive checked out the
strerror linux manual page, but it didnt give me any clues as to what might be calling it.