Typically there's a report with a repro test case and an indication of the stack trace where it happened.

My experience is that it's generally pretty easy to nail down what's going on (assuming experience with the code base) unless it's something subtle with library dependency versions where it's not showing up under valgrind, only in their tool, in their docker container.