Le mer. 17 janv. 2024 à 02:02, Paul Floyd <pjfl...@wanadoo.fr> a écrit :
>
>
> 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
>
>
Thank you for your answer.
Unfortunately, I'm stuck with valgrind 3.19 for some reason.
I'm not modifying any thread priorities or scheduling.
Before your answer, I tried a couple of things. And I discovered that if I
create a non-member function
that will call Class::MemberFunction, and use that 'global' function as the
thread entry point, then the
thread is created and executed...
So, creating the thread with a line like:
auto thread = new std::thread(NonMemberFunction, this, ptr1, ptr2);
and with
void
NonMemberFunction(Class *ptr_to_instance, Ptr1 *ptr1, Ptr2 *ptr2)
{
ptr_to_instance->MemberFunction(ptr1, ptr2);
}
will work...
Hope that could be useful if other people face the same thing.
So the problem looks to be related to issues with creating threads with
bound member functions.
I'll try the --fair-sched=yes option and keep posted here in case that
fixes the issue.
Cheers.
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
