[HN Gopher] Libtree: Ldd as a tree saying why a library is found...
       ___________________________________________________________________
        
       Libtree: Ldd as a tree saying why a library is found or not
        
       Author : fanf2
       Score  : 45 points
       Date   : 2024-06-09 19:42 UTC (3 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | mgaunard wrote:
       | this is so useful; I usually read sections with readelf to figure
       | out what the real requirements are
        
       | monocasa wrote:
       | Does this copy that unexpected behavior where ldd will actually
       | execute some libraries it's interrogating?
       | 
       | https://catonmat.net/ldd-arbitrary-code-execution
        
         | jcul wrote:
         | From a quick scan of the code, on mobile, it doesn't look like
         | it does.
         | 
         | This seems to actually manually parse the ELF file and
         | recursively parse any dependencies.
         | 
         | Pretty cool.
        
       | jononor wrote:
       | Having to recursively and iteratively hunt missing dependencies
       | with ldd can be pretty tedious. So this seems like a good
       | improvement. Will try it next time I get an obscure not found
        
       | userbinator wrote:
       | Basically the Linux CLI version of depends.exe.
        
       | clumsysmurf wrote:
       | Anyone know of something similar for MacOS?
        
       | khoobid_shoma wrote:
       | It's great that the implementation is in C and not in less
       | efficient but fashionable languages.
        
         | heinrich5991 wrote:
         | C++, Nim, Rust, Zig would probably work as well.
        
       ___________________________________________________________________
       (page generated 2024-06-09 23:00 UTC)