Add a debugging mode which gives each use of a constructor a distinct info table
At the moment you can quite precisely track down THUNK and function allocations by looking at the address of the info table and dwarf information but allocations due to constructors are hard to identify precisely because they all share the same info table and hence one allocated are impossible to tell apart.
Therefore the idea is that for each usage of constructor we generate a distinct info table so that each allocation site can be distinguished easily. Then using DWARF information it is easy to map the addresses of specific constructor info tables to a source location so from a profile you can easily see exactly where the residency comes from.
Related to the "profiling by info table" idea. #18160