On Thu, Jun 12, 2014 at 10:15 PM, H. Peter Anvin <h...@zytor.com> wrote: > On 06/12/2014 09:36 PM, Andy Lutomirski wrote: >> >> If we were to implement both, maybe we'd actually want to provide >> something like: >> >> struct vdso_entry { >> unsigned long vdso_entry_struct_size; /* so we can add fields later on */ >> void *func; >> unsigned int max_stack; /* zero if not known */ >> }; >> > > How different is this really from the .dynsym table -- other than that > you have to find the latter via the dynamic segment? > > The hash part is just to speed up lookup...
As far as I know, there's no reliable way to just read the dynsym table -- the thing doesn't have a specified length, which is what broke Go in the first place. Parsing the ELF dynamic tables is kind of annoyingly complicated, and understanding the format is a real PITA -- the documentation I've been able to find is outright terrible. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/