search for: dl_init

...it is not possible to do this for __heapprof_init, as it calls timespec_get in order to get a baseline timestamp (as described in the ChunkHeader comments the timestamps (ms) are actually offsets from the baseline timestamp, in order to fit into 32 bits), and system calls cannot be made that early (dl_init is not complete). Since the constructor priority is 1, it should be executed early enough that there are very few allocations before it runs, and likely the best solution is to simply ignore any allocations before initialization. Dumping For the prototype, the profile is dumped as text with a comp...

...o do this for __heapprof_init, as it calls > timespec_get in order to get a baseline timestamp (as described in the > ChunkHeader comments the timestamps (ms) are actually offsets from the > baseline timestamp, in order to fit into 32 bits), and system calls cannot > be made that early (dl_init is not complete). Since the constructor > priority is 1, it should be executed early enough that there are very few > allocations before it runs, and likely the best solution is to simply > ignore any allocations before initialization. > Dumping > > For the prototype, the profile...

...this for __heapprof_init, as it > calls timespec_get in order to get a baseline timestamp (as described > in the ChunkHeader comments the timestamps (ms) are actually offsets > from the baseline timestamp, in order to fit into 32 bits), and system > calls cannot be made that early (dl_init is not complete). Since the > constructor priority is 1, it should be executed early enough that > there are very few allocations before it runs, and likely the best > solution is to simply ignore any allocations before initialization. > > > Dumping > > For the prot...

...heapprof_init, as it calls >> timespec_get in order to get a baseline timestamp (as described in the >> ChunkHeader comments the timestamps (ms) are actually offsets from the >> baseline timestamp, in order to fit into 32 bits), and system calls cannot >> be made that early (dl_init is not complete). Since the constructor >> priority is 1, it should be executed early enough that there are very few >> allocations before it runs, and likely the best solution is to simply >> ignore any allocations before initialization. >> Dumping >> >> For the...