...Drat, I thought I had it this time. Oh well, sorry to make a mess
again.
The following changes since commit
6f447ef7f0c5000e88d11312c06df9d5021d4ecd:
libdwfl: don't bother freeing frames outside of dwfl_thread_getframes
(2019-10-29 17:48:05 +0100)
are available in the Git repository at
Hi Jonathon,
On Tue, Oct 29, 2019 at 01:55:25PM -0500, Jonathon Anderson wrote:
> This is (revived and rebased) version of the libdw memory manager that isn't
> affected by the PTHREAD_KEYS_MAX limit. There are some downsides, in
> particular if an application spawns many short-lived threads that
[PATCH 2/2] libdw: Rewrite the memory handler to be more robust.
Pthread's thread-local variables are highly limited, which makes
it difficult to use many Dwarfs. This replaces that with a
less efficient (or elegant) but more robust method.
Signed-off-by: Jonathon Anderson
---
lib/atomics.h
[PATCH 1/2] Add configure options for Valgrind annotations.
Signed-off-by: Jonathon Anderson
---
ChangeLog| 5 +
configure.ac | 30 ++
2 files changed, 35 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index 911cf354..433a5f3c 100644
--- a/ChangeLog
+++ b/Ch
Hello,
This is (revived and rebased) version of the libdw memory manager that
isn't affected by the PTHREAD_KEYS_MAX limit. There are some downsides,
in particular if an application spawns many short-lived threads that
all touch a Dwarf (enough to cause an allocation), there's about ~8N
bytes
