Mark,
A third option that Heather and I discussed for the routines that needed
replication (because sometimes they are called holding a write lock and
sometimes not) was to put each routine in an include file where the write lock
status is expected to be defined as a macro. Then, we can define
I've been making --enable-thread-safety (USE_LOCKS) more viable by fixing
deadlocks throughout the libelf library. This has required minimal code
changes so far. However, I've hit a snag where "__elf64_updatenull_wrlock"
calls "elf64_getchdr," which leads to "elf64_getshdr." This sequence
attempts
