5 ms·

Article is dated 2009. Previous discussions: - [2009] https://news.ycombinator.com/item?id=902958 https://news.ycombinator.com/item?id=902958 - [2015] https:

• a1o 3y ago
  Is the mentioned issue in the article still true today?
  • eqvinox 3y ago
    Yes. So is the (IMHO) best workaround of using lddtree (pax-utils) instead. Available on pretty much all distros, though probably not installed by default.
    • anthk 3y ago
      objdump -x /path/to/bin | grep NEEDED
      • eqvinox 3y ago
        Doesn't tell you if/where the library is found on your system.
        • janAkali 3y ago
          for i in $(objdump -p /path/to/bin | grep NEEDED | awk '{print $2}'); do ldconfig -p | awk -v var="$i" '$1==var{print $0}'; done edit: even simpler, for i in $(objdump -p /path/to/bin | grep NEEDED | awk '{print $2}'); do ldconfig -p | grep $i; done
          • eqvinox 3y ago
            Cool, but I think I'll stick to lddtree ;) (… it also recurses down on the dependencies, presumably you can extend your shell script to do that too but at some point why not just use the existing tools?)
  • mid-kid 3y ago
    Not in glibc at least[1], and I reckon many other implementations don't have this problem either. [1]: https://manpages.debian.org/bookworm/manpages/ldd.1.en.html#Security https://manpages.debian.org/bookworm/manpages/ldd.1.en.html#...