Re: x86_64: vsyscall vs vdso

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/17/07, Francis Moreau <[email protected]> wrote:
> Actually if we could easily retrieve the vdso in a process memory
> mapping (through a new syscall or /proc/self/maps), it should be easy
> for gcc/ld to statically links vdso functions into a statically linked
> app, shouldn't it ?

Nonsense.  All the code which is in the vdso has a real implementation
in libc.  No need to substitute.  The vdso is only there to adjust a
program to the actual environment in which it is executed and not in
which it is built.  Your suggestion would do the latter which is
complete and utter nonsense.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux