I’m running last nights nightly build on Linux x86_64 and am using the leak sanitizer to trace down a slow leak.
The output indicates the leaked memory is coming from a C function. There are only two frames shown in the sanitizer output, the C function and one from lsan itself. Unfortunately, that C function is getting called indirectly in many locations making it hard to find the culprit in my Rust code.
Is there a way to convince lsan to output frames before the allocation to give me more context?