$ LD_DEBUG=statistics nmap -V
32564: total startup time in dynamic loader: 8917260 cycles
32564: final number of relocations: 2449
$ LD_BIND_NOW=1 LD_DEBUG=statistics nmap -V
32565: total startup time in dynamic loader: 12511900 cycles
32565: final number of relocations: 4730
Another difference between lazy and now is that if there is some symbol resolution problem, but the application never actually references that symbol, then the process can still run. This is either an advantage or a disadvantage depending on how you look at it.How does one acquire (and retain) this depth of knowledge. I work on low-level system software (C programming). Having good understanding of build system (make, cmake), dependencies and shared library knowledge is highly desired in my field.
But this is very hard core. Really interested in the path leading up to this.
If you want to learn, it is not hard at all. All it takes is curiosity. Of course, hitting a bug in ld.so or having to debug a kinky issue at the instruction level can feed such curiosity.
Apart from that, being in the right place helps. That could be a mailing list or some other channel where these tools are talked about.
Out of curiosity, what software do you work on? I have a very difficult time finding a C job, let alone one where this type of information would be valued.
I work in networking industry (as software dev). Think Juniper, Cisco, Brocade etc. This industry needs only C devs.