From: Paul F. <pj...@wa...> - 2024-01-17 07:00:37
|
On 16/01/2024 20:17, JD Silence wrote: > Hello, > > I'm looking for some hints, advice and any other things that could > help me figure this out. > > I have a big program which I wanted to debug some memory issues. This > program internally creates and runs several threads. > [snip] > The program is written in C++ 20. That particular problematic thread > is simply created by a line like: > > auto thread = new std::thread(&Class::MemberFunction, this, ptr1, ptr2); > > So nothing fancy, in my opinion. The debugger reaches that line, and a > press to next never enters the breakpoint set in Class::MemberFunction. > > In case that could matter, I'm using valgrind 3.19.0 on Debian 12. > Not much has changed to the threading/scheduling, unless you are changing the thread attributes for priority/scheduling. If so then you should try Valgrind 3.22. Otherwise, try --fair-sched=yes A+ Paul |