On Sun, 2022-09-04 at 00:14 +0200, Tomas Vondra wrote: > > Clearly, this is not an issue valgrind is meant to detect (like invalid > memory access, etc.) but an application issue. I've tried reproducing it > without valgrind, but it only ever happens with valgrind - my theory is > it's some sort of race condition, and valgrind changes the timing in a > way that makes it much more likely to hit. I need to analyze the core to > inspect the state more closely, etc. > > Any ideas what I might be doing wrong? Or how do I load the core file?
Rather than have the core dump and analyse it, you might interactively debug your program under valgrind. E.g. you might put a breakpoint on the assert or at some interesting points before the assert. See https://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver for more info. Philippe _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
