Rod,
I know I can use 'grep' to filter out information I need.
But It takes quite a long time to generate output file when there
are a lot of static libraries to link.
Brian
On 08/ 9/10 11:19 PM, Rod Evans wrote:
On 8/9/10 2:56 AM, Brian Lu wrote:
Hi, All,
Link editor and runtime linker provide a very useful debugging facility.
I can use LD_DEBUG=symbols,detail and LD_OPTIONS=-Dsymbols,detail
to find out all symbols processing information in ld.so.1 or ld.
I need to save the output to a file first. So when there are a lot of
libraries processed, the result file will be very large. But sometimes,
I only interested in some specific symbols, is there any way that I can
tell the ld.so.1 or ld to dump
only information related to those symbols instead of all symbols?
Nope sorry.
I find that most "debugging" activities require obtaining a number
of pieces of information, a symbol, then perhaps the files that
offer and use that symbol, etc. The debug output is created with
a mind to "grep" for information from it.
With the latest linkers you can identify an output file as a token:
LD_OPTIONS=-D<tok1>,<tok2>,output=dbg
You can use this same syntax with LD_DEBUG, but if the process
forks than all processes are captured in the same file, which can
be hard to unravel. ld.so.1 continues to use LD_DEBUG_OUTPUT=dbg
to create a dbg.{pid} file for each process being monitored.
_______________________________________________
tools-linking mailing list
[email protected]
