On Tue, Jul 01, 2014 at 07:09:46AM -0700, Andy Lutomirski wrote:
On Tue, Jul 1, 2014 at 7:01 AM, Nathan Lynch [off-list ref] wrote:
quoted
Hmm, which tools? Shouldn't they be consulting AT_SYSINFO_EHDR in the
auxiliary vector instead?
There were a bunch of random things written before getauxvec(3) was
introduced that look for "[vdso]"
gdb is also a bit weird. I think it's changed a couple times, but
IIRC it looks for a vma that has a start address that matches
AT_SYSINFO_EDHR, and then it parses the ELF header and *section*
headers (sigh) in that vma. So if I'm remembering correctly, it just
won't notice the vdso at all of AT_SYSINFO_EHDR and the vma start
aren't the same.
Hmm, that would explain the weird error I got when trying gdb with the
vdso in place.
--
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.