Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 10-10-24 11:16, Konstantin Belousov wrote:

> If you can determine not just the number of taken locks, but also the
> specific locks that were taken, perhaps you can check that this is
> the libc exit lock?

For the moment I've turned off the check for FreeBSD 15 and above.

At present the ExeContext is not saved for each lock. Each thread has a 
set of held lock IDs. It might be useful to change that, depending on 
the memory and time overhead.

I'll try to see if there is an efficient way to check that the 
ExeContext for pthread_mutex_lock is exit/__libc_start1.

A+
Paul