"LD_DEBUG" does not include a "TLS" event tracking option.

Solution Verified - Updated -

Issue

  • When a library is loaded and relocated as part of an application and it has TLS memory that it updates then the library is dynamically loaded with dlopen(), the second load can change the generation counter leaving the library's TLS area set as unallocated causing it to be reallocated the next time that it is used. This results in any information that had been stored in the TLS before the dlopen() of the library being lost, hence the need for a TLS event tracking option.

  • To debug TLS issues, it is required to have information like TLS initialization, thread creation and its "dtv", updating the generation counter, when a library is loaded the size of the "PT_TLS" that the library requests(since IE TLS is so limited), etc. Hence, to track down these events need an enhancement is needed to include TLS in "LD_DEBUG".

Environment

  • Red Hat Enterprise Linux 9.4
  • glibc

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content