Messages in this thread | | | Date | Thu, 14 Aug 2008 10:15:29 -0700 | From | Ulrich Drepper <> | Subject | AT_EXECFN not useful |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I've just removed the support for AT_EXECFN again from glibc. The information isn't useful because the path name isn't normalized. I.e., it's not the actual binary path if symlinks are followed during the resolution. This makes it unusable for the $ORIGIN handling. This is on top of the problem with relative paths.
Unless somebody has another use case where this is useful I suggest removing AT_EXECFN support again. It's just superfluous work and memory use.
Of course I wouldn't object to a real implementation which always gives me the full, normalized path name of the executable...
- -- ➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkikaDEACgkQ2ijCOnn/RHSFvACgoWYhqrfJZfRe4ypFUQQR9soJ km8AnRchCWP+irhGcgoSzd2S8iYQi7zm =E4tz -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |