This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 06/20/2016 11:04 AM, Andreas Schwab wrote:
Florian Weimer <fweimer@redhat.com> writes:Could we export a single symbol which is a struct and contains all the data we need? Then the impact on dynamic symbol table size would be minimal.That would raise the issue of compatibility. Probing each symbol separately is much easier than trying to extend the struct. What exactly _is_ the impact of making the dynamic symtab a few entries bigger?
Does compatibility really matter? I thought you need exactly matching libpthread and libthread_db versions anyway. I suppose we could even compile the offsets into libthread_db.
I assume that for compatibility across multiple versions, we will need something like Infinity.
Thanks, Florian
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |