LLD solves the problem of program startup dependent Libraries

Scenario Description: It is very troublesome to find the dependent libraries of programs. If you need some unused libraries, it is very difficult to transplant the entire system. At present, I try to use LLD to find all dependent libraries, then extract these dependent libraries, put them in the same folder, and then define the dependency path to solve the problem.

 

LDD [Option] File

Options include-V: print the version number of LDD;-D: Execute the symbol re-deployment, and report the missing target object (only applicable to the ELF format);-R: redeploy the target object and function, and report the missing target object and function (applicable only to the ELF format);-H: help information.

Run the following command to view the database associated with the application:

LDD-V program name